I want to announce that node.js powers Plurk's new comet system. Plurk
is one of Asia's largest micro-blogs with millions of users.
We have rewritten to node.js from Java+JBoss Netty, because the old
solution had scalability problems. We have also been able to build a
very sophisticated messaging system given JavaScript expressiveness
and the simplicity of node.js. Generally, we have found node.js and V8
_very_ impressive - - and it uses about 10 times _less_ memory than
Java+Netty did.
Stats of this system:
* hundred thousands of online users at once
* huge amount of usage - to this day our users have posted over 1
billion unique messages
* uses only one server (a quad core with 32GB of RAM, but node.js uses
only a few GB)
I will probably wrap these up in a more detailed post in the future.
More info can be read here (along with links on comet related articles
that I have shared):
http://amix.dk/blog/post/19490#Plurk-Instant-conversations-using-comet
Like I announced here before I held a presentation on comet with
node.js and V8 to the Taipei Open Source group, it can be viewed here:
http://amix.dk/blog/post/19484
We may release our comet implementation in the future - but currently
it's very tied up to Plurk's architecture.
Kind regards,
amix - lead dev of Plurk
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> I want to announce that node.js powers Plurk's new comet system. Plurk
> is one of Asia's largest micro-blogs with millions of users.
Nice! Is it a public information what backend database are you using
for storing the messages? I guess it's not just in the memory of node.
:)
Bye,
Andras
I have answered some questions here which have a relation to this:
http://news.ycombinator.com/item?id=1088699
Kind regards,
amix
Kind regards,
amix
> --
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en.
>
>
--
Sent from my mobile device
The thing to note thought is that it's not that hard to keep many
connections open if they are inactive most of the time.
A more serious scalability problem is to have 200k+ _active_
connections at once (active defined as you are writing data to them
most of the time)... Luckily we don't have this problem ;-)
Kind regards,
amix
I have done some benchmarks along this lines. i.e. if you have 10k
open connections, how long does it take to send each client a message?
You'll find that at 10k connections it can take up to 1.5sec to get
the message to the last client:
https://gist.github.com/73631cd1ffaa957e017a
I'll publish more in-depth analysis after net2 is merged.
HTH,
-- fg