<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: jboss</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/jboss.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-02-01T10:13:14+00:00</updated><author><name>Simon Willison</name></author><entry><title>Plurk: Instant conversations using Comet</title><link href="https://simonwillison.net/2010/Feb/1/plurk/#atom-tag" rel="alternate"/><published>2010-02-01T10:13:14+00:00</published><updated>2010-02-01T10:13:14+00:00</updated><id>https://simonwillison.net/2010/Feb/1/plurk/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://amix.dk/blog/post/19490"&gt;Plurk: Instant conversations using Comet&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Plurk’s comet implementation sounds pretty amazing. They’re using a single quad-core server with 32GB of RAM running 8 Node.js instances to serve long-polled comet to 100,000+ simultaneous users. They switched to Node from Java JBoss/Netty and found the new solution used 10 times less memory.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://news.ycombinator.com/item?id=1088699"&gt;Hacker News&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/comet"&gt;comet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/java"&gt;java&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jboss"&gt;jboss&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/netty"&gt;netty&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/nodejs"&gt;nodejs&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/plurk"&gt;plurk&lt;/a&gt;&lt;/p&gt;



</summary><category term="comet"/><category term="java"/><category term="javascript"/><category term="jboss"/><category term="netty"/><category term="nodejs"/><category term="plurk"/></entry></feed>