Re: [nodejs] Hook.io performance

[Alexey Kupershtokh]

> If you require more then 666.66 messages per second out of the box, you 
> should not be using dnode as your message transport. hook.io currently 
> uses dnode as it's primary message transport.
>

Totally agree with you here. I'm developing a social game server-side 
cluster. We are using socket.io on the servers and flashsocket.io on the 
client. After comparing dnode and socket.io using benchmarks for server to 
server communications I selected socket.io here as well. I don't remember 
exact numbers now but I believe socket.io was about 10 times faster.

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Hook.io performance

[Dan Milon]

At start i mean one time before we go live, its a migration, but the 
messages have to go through node so it generates some data.


Thanks Marak!

On 07/02/2012 02:25 AM, Marak Squires wrote:

Wow That is a lot of messages.

I'd recommend trying to re-architect the solution you are building. It 
doesn't seem like a good idea to use dnode ( or even the node net 
module ) to pass that many messages on start.


If you want to use node, you'll probably need to bring in an add-on 
that links to a more robust messaging protocol.


On Sun, Jul 1, 2012 at 4:11 PM, Dan Milon > wrote:


30 million messages :/


On 07/02/2012 02:11 AM, Marak Squires wrote:

Err, is ~30mil 30 milliseconds or 30 million messages?

On Sun, Jul 1, 2012 at 4:10 PM, Marak Squires
mailto:marak.squi...@gmail.com>
>> wrote:

How far off are you from hitting your 30ms latency target?

You could probably just use redis, or 0mq with a node.js
driver.

On Sun, Jul 1, 2012 at 3:45 PM, Dan Milon
mailto:danmi...@gmail.com>
>>
wrote:

Hey Marak,

Thanks for the valuable info.
The use case is: I have a few hooks that receive
messages each
one from a different source (rabbitMQ, http) and there
is a
central hook that receives all those messages, does some
calculations and stores into a database.

Truth is, our message rate is quite lower than 600
msg/s but i
need to pass in some initial data which are ~30mil, so
that
means i will have to write separate code to do just this,
without hook.io  .


I could also pack all that stuff into one process and
get over
it, but then i wouldn't make use of multicore etc.
Do you know other communication/IPC libraries i could look
into, or got any other suggestion?

Thanks,
danmilon.

On 07/02/2012 01:35 AM, Marak Squires wrote:

As of today, I've done literally no performance
optimizations for hook.io 
 .

hook.io   's
power is in

API and discovery.

If you require more then 666.66 messages per
second out of
the box, you should not be using dnode as your message
transport. hook.io 
 

currently uses dnode as it's primary message
transport.

hook.io    is
intended to

be multi-transport, so for high performance situations
you'd want to use hook.io 

 as a wrapper around a more robust
solution like 0mq.

If do you don't mind, I'd be interested in hearing
what
your intended use case for hook.io
 
 was which would require that
throughput.
Always good to get more input to shape the API.


On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon
mailto:danmi...@gmail.com>
>
 
 

for some project.
Today i thought of measuring how fast hook.io

  can


emit and receive messages, so i built a dead
simple
benchmark [1],
and numbers are not that interesting.
It took 15 secs to deliver 10k messages from
one hook
to another.

I do not know the underlaying mechanisms
hook.io 
 


uses for IPC (please enlighten me), but isn't this
performance
quite low? Or is there somet

Re: [nodejs] Hook.io performance

[Marak Squires]

Wow That is a lot of messages.

I'd recommend trying to re-architect the solution you are building. It
doesn't seem like a good idea to use dnode ( or even the node net module )
to pass that many messages on start.

If you want to use node, you'll probably need to bring in an add-on that
links to a more robust messaging protocol.

On Sun, Jul 1, 2012 at 4:11 PM, Dan Milon  wrote:

> 30 million messages :/
>
>
> On 07/02/2012 02:11 AM, Marak Squires wrote:
>
>> Err, is ~30mil 30 milliseconds or 30 million messages?
>>
>> On Sun, Jul 1, 2012 at 4:10 PM, Marak Squires 
>> > marak.squires@gmail.**com >> wrote:
>>
>> How far off are you from hitting your 30ms latency target?
>>
>> You could probably just use redis, or 0mq with a node.js driver.
>>
>> On Sun, Jul 1, 2012 at 3:45 PM, Dan Milon > > wrote:
>>
>> Hey Marak,
>>
>> Thanks for the valuable info.
>> The use case is: I have a few hooks that receive messages each
>> one from a different source (rabbitMQ, http) and there is a
>> central hook that receives all those messages, does some
>> calculations and stores into a database.
>>
>> Truth is, our message rate is quite lower than 600 msg/s but i
>> need to pass in some initial data which are ~30mil, so that
>> means i will have to write separate code to do just this,
>> without hook.io .
>>
>>
>> I could also pack all that stuff into one process and get over
>> it, but then i wouldn't make use of multicore etc.
>> Do you know other communication/IPC libraries i could look
>> into, or got any other suggestion?
>>
>> Thanks,
>> danmilon.
>>
>> On 07/02/2012 01:35 AM, Marak Squires wrote:
>>
>> As of today, I've done literally no performance
>> optimizations for hook.io  .
>>
>> hook.io  's power is in
>>
>> API and discovery.
>>
>> If you require more then 666.66 messages per second out of
>> the box, you should not be using dnode as your message
>> transport. hook.io  
>>
>> currently uses dnode as it's primary message transport.
>>
>> hook.io   is intended to
>>
>> be multi-transport, so for high performance situations
>> you'd want to use hook.io 
>>  as a wrapper around a more robust
>> solution like 0mq.
>>
>> If do you don't mind, I'd be interested in hearing what
>> your intended use case for hook.io 
>>  was which would require that throughput.
>> Always good to get more input to shape the API.
>>
>>
>> On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon
>> mailto:danmi...@gmail.com>
>> >>
>> wrote:
>>
>> Hello,
>>
>> I am using hook.io  
>>
>> for some project.
>> Today i thought of measuring how fast hook.io
>>   can
>>
>>
>> emit and receive messages, so i built a dead simple
>> benchmark [1],
>> and numbers are not that interesting.
>> It took 15 secs to deliver 10k messages from one hook
>> to another.
>>
>> I do not know the underlaying mechanisms hook.io
>>  
>>
>>
>> uses for IPC (please enlighten me), but isn't this
>> performance
>> quite low? Or is there something wrong with the test?
>>
>> Thanks,
>> Dan Milon.
>>
>> [1] 
>> https://gist.github.com/**3029842
>>
>> -- Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/**node/wiki/Mailing-List-**
>> Posting-Guidelines
>> You received this message because you are subscribed
>> to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to
>> nodejs@googlegroups.com 
>> > >
>> >
>> >
>>
>> To unsubscribe from this group, send email to
>> 
>> nodejs+unsubscribe@**googlegroups.com
>> 
>> > >
>> 
>> 

Re: [nodejs] Hook.io performance

[Dan Milon]

30 million messages :/

On 07/02/2012 02:11 AM, Marak Squires wrote:

Err, is ~30mil 30 milliseconds or 30 million messages?

On Sun, Jul 1, 2012 at 4:10 PM, Marak Squires > wrote:


How far off are you from hitting your 30ms latency target?

You could probably just use redis, or 0mq with a node.js driver.

On Sun, Jul 1, 2012 at 3:45 PM, Dan Milon mailto:danmi...@gmail.com>> wrote:

Hey Marak,

Thanks for the valuable info.
The use case is: I have a few hooks that receive messages each
one from a different source (rabbitMQ, http) and there is a
central hook that receives all those messages, does some
calculations and stores into a database.

Truth is, our message rate is quite lower than 600 msg/s but i
need to pass in some initial data which are ~30mil, so that
means i will have to write separate code to do just this,
without hook.io .

I could also pack all that stuff into one process and get over
it, but then i wouldn't make use of multicore etc.
Do you know other communication/IPC libraries i could look
into, or got any other suggestion?

Thanks,
danmilon.

On 07/02/2012 01:35 AM, Marak Squires wrote:

As of today, I've done literally no performance
optimizations for hook.io  .

hook.io  's power is in
API and discovery.

If you require more then 666.66 messages per second out of
the box, you should not be using dnode as your message
transport. hook.io  
currently uses dnode as it's primary message transport.

hook.io   is intended to
be multi-transport, so for high performance situations
you'd want to use hook.io 
 as a wrapper around a more robust
solution like 0mq.

If do you don't mind, I'd be interested in hearing what
your intended use case for hook.io 
 was which would require that throughput.
Always good to get more input to shape the API.


On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon
mailto:danmi...@gmail.com>
>>
wrote:

Hello,

I am using hook.io  
for some project.
Today i thought of measuring how fast hook.io
  can

emit and receive messages, so i built a dead simple
benchmark [1],
and numbers are not that interesting.
It took 15 secs to deliver 10k messages from one hook
to another.

I do not know the underlaying mechanisms hook.io
 

uses for IPC (please enlighten me), but isn't this
performance
quite low? Or is there something wrong with the test?

Thanks,
Dan Milon.

[1] https://gist.github.com/3029842

-- Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed
to the Google
Groups "nodejs" group.
To post to this group, send email to
nodejs@googlegroups.com 
>

To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com

>

For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en


-- 
Job Board: http://jobs.nodejs.org/

Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to
the Google
Groups "nodejs" group.
To post to this group, send email to
nodejs@googlegroups.com 
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com

For more options, visit this group at

Re: [nodejs] Hook.io performance

[Marak Squires]

Err, is ~30mil 30 milliseconds or 30 million messages?

On Sun, Jul 1, 2012 at 4:10 PM, Marak Squires wrote:

> How far off are you from hitting your 30ms latency target?
>
> You could probably just use redis, or 0mq with a node.js driver.
>
> On Sun, Jul 1, 2012 at 3:45 PM, Dan Milon  wrote:
>
>> Hey Marak,
>>
>> Thanks for the valuable info.
>> The use case is: I have a few hooks that receive messages each one from a
>> different source (rabbitMQ, http) and there is a central hook that receives
>> all those messages, does some calculations and stores into a database.
>>
>> Truth is, our message rate is quite lower than 600 msg/s but i need to
>> pass in some initial data which are ~30mil, so that means i will have to
>> write separate code to do just this, without hook.io.
>>
>> I could also pack all that stuff into one process and get over it, but
>> then i wouldn't make use of multicore etc.
>> Do you know other communication/IPC libraries i could look into, or got
>> any other suggestion?
>>
>> Thanks,
>> danmilon.
>>
>> On 07/02/2012 01:35 AM, Marak Squires wrote:
>>
>>> As of today, I've done literally no performance optimizations for
>>> hook.io .
>>>
>>> hook.io 's power is in API and discovery.
>>>
>>> If you require more then 666.66 messages per second out of the box, you
>>> should not be using dnode as your message transport. hook.io <
>>> http://hook.io> currently uses dnode as it's primary message transport.
>>>
>>> hook.io  is intended to be multi-transport, so for high
>>> performance situations you'd want to use hook.io  as a
>>> wrapper around a more robust solution like 0mq.
>>>
>>> If do you don't mind, I'd be interested in hearing what your intended
>>> use case for hook.io  was which would require that
>>> throughput. Always good to get more input to shape the API.
>>>
>>>
>>> On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon >> danmi...@gmail.com>> wrote:
>>>
>>> Hello,
>>>
>>> I am using hook.io  for some project.
>>> Today i thought of measuring how fast hook.io  can
>>>
>>> emit and receive messages, so i built a dead simple benchmark [1],
>>> and numbers are not that interesting.
>>> It took 15 secs to deliver 10k messages from one hook to another.
>>>
>>> I do not know the underlaying mechanisms hook.io 
>>>
>>> uses for IPC (please enlighten me), but isn't this performance
>>> quite low? Or is there something wrong with the test?
>>>
>>> Thanks,
>>> Dan Milon.
>>>
>>> [1] https://gist.github.com/**3029842
>>>
>>> -- Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/**node/wiki/Mailing-List-**
>>> Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> 
>>>
>>> To unsubscribe from this group, send email to
>>> 
>>> nodejs+unsubscribe@**googlegroups.com
>>> 
>>> >> >
>>>
>>> For more options, visit this group at
>>> 
>>> http://groups.google.com/**group/nodejs?hl=en?hl=en
>>>
>>>
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-*
>>> *Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscribe@**googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/**group/nodejs?hl=en?hl=en
>>>
>>
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-**
>> Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscribe@**googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/**group/nodejs?hl=en?hl=en
>>
>
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googl

Re: [nodejs] Hook.io performance

[Marak Squires]

How far off are you from hitting your 30ms latency target?

You could probably just use redis, or 0mq with a node.js driver.

On Sun, Jul 1, 2012 at 3:45 PM, Dan Milon  wrote:

> Hey Marak,
>
> Thanks for the valuable info.
> The use case is: I have a few hooks that receive messages each one from a
> different source (rabbitMQ, http) and there is a central hook that receives
> all those messages, does some calculations and stores into a database.
>
> Truth is, our message rate is quite lower than 600 msg/s but i need to
> pass in some initial data which are ~30mil, so that means i will have to
> write separate code to do just this, without hook.io.
>
> I could also pack all that stuff into one process and get over it, but
> then i wouldn't make use of multicore etc.
> Do you know other communication/IPC libraries i could look into, or got
> any other suggestion?
>
> Thanks,
> danmilon.
>
> On 07/02/2012 01:35 AM, Marak Squires wrote:
>
>> As of today, I've done literally no performance optimizations for hook.io<
>> http://hook.io>.
>>
>> hook.io 's power is in API and discovery.
>>
>> If you require more then 666.66 messages per second out of the box, you
>> should not be using dnode as your message transport. hook.io <
>> http://hook.io> currently uses dnode as it's primary message transport.
>>
>> hook.io  is intended to be multi-transport, so for high
>> performance situations you'd want to use hook.io  as a
>> wrapper around a more robust solution like 0mq.
>>
>> If do you don't mind, I'd be interested in hearing what your intended use
>> case for hook.io  was which would require that
>> throughput. Always good to get more input to shape the API.
>>
>>
>> On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon > danmi...@gmail.com>> wrote:
>>
>> Hello,
>>
>> I am using hook.io  for some project.
>> Today i thought of measuring how fast hook.io  can
>>
>> emit and receive messages, so i built a dead simple benchmark [1],
>> and numbers are not that interesting.
>> It took 15 secs to deliver 10k messages from one hook to another.
>>
>> I do not know the underlaying mechanisms hook.io 
>>
>> uses for IPC (please enlighten me), but isn't this performance
>> quite low? Or is there something wrong with the test?
>>
>> Thanks,
>> Dan Milon.
>>
>> [1] https://gist.github.com/**3029842
>>
>> -- Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/**node/wiki/Mailing-List-**
>> Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> 
>>
>> To unsubscribe from this group, send email to
>> 
>> nodejs+unsubscribe@**googlegroups.com
>> 
>> > >
>>
>> For more options, visit this group at
>> 
>> http://groups.google.com/**group/nodejs?hl=en?hl=en
>>
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-**
>> Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscribe@**googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/**group/nodejs?hl=en?hl=en
>>
>
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-**
> Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@**googlegroups.com
> For more options, visit this group at
> http://groups.google.com/**group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Hook.io performance

[Dan Milon]

Hey Marak,

Thanks for the valuable info.
The use case is: I have a few hooks that receive messages each one from 
a different source (rabbitMQ, http) and there is a central hook that 
receives all those messages, does some calculations and stores into a 
database.


Truth is, our message rate is quite lower than 600 msg/s but i need to 
pass in some initial data which are ~30mil, so that means i will have to 
write separate code to do just this, without hook.io.


I could also pack all that stuff into one process and get over it, but 
then i wouldn't make use of multicore etc.
Do you know other communication/IPC libraries i could look into, or got 
any other suggestion?


Thanks,
danmilon.

On 07/02/2012 01:35 AM, Marak Squires wrote:
As of today, I've done literally no performance optimizations for 
hook.io .


hook.io 's power is in API and discovery.

If you require more then 666.66 messages per second out of the box, 
you should not be using dnode as your message transport. hook.io 
 currently uses dnode as it's primary message transport.


hook.io  is intended to be multi-transport, so for 
high performance situations you'd want to use hook.io  
as a wrapper around a more robust solution like 0mq.


If do you don't mind, I'd be interested in hearing what your intended 
use case for hook.io  was which would require that 
throughput. Always good to get more input to shape the API.


On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon > wrote:


Hello,

I am using hook.io  for some project.
Today i thought of measuring how fast hook.io  can
emit and receive messages, so i built a dead simple benchmark [1],
and numbers are not that interesting.
It took 15 secs to deliver 10k messages from one hook to another.

I do not know the underlaying mechanisms hook.io 
uses for IPC (please enlighten me), but isn't this performance
quite low? Or is there something wrong with the test?

Thanks,
Dan Milon.

[1] https://gist.github.com/3029842

-- 
Job Board: http://jobs.nodejs.org/

Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com

To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en


--
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en



--
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Hook.io performance

[Marak Squires]

As of today, I've done literally no performance optimizations for hook.io.

hook.io's power is in API and discovery.

If you require more then 666.66 messages per second out of the box, you
should not be using dnode as your message transport. hook.io currently uses
dnode as it's primary message transport.

hook.io is intended to be multi-transport, so for high performance
situations you'd want to use hook.io as a wrapper around a more robust
solution like 0mq.

If do you don't mind, I'd be interested in hearing what your intended use
case for hook.io was which would require that throughput. Always good to
get more input to shape the API.

On Sun, Jul 1, 2012 at 3:18 PM, Dan Milon  wrote:

> Hello,
>
> I am using hook.io for some project.
> Today i thought of measuring how fast hook.io can emit and receive
> messages, so i built a dead simple benchmark [1], and numbers are not that
> interesting.
> It took 15 secs to deliver 10k messages from one hook to another.
>
> I do not know the underlaying mechanisms hook.io uses for IPC (please
> enlighten me), but isn't this performance quite low? Or is there something
> wrong with the test?
>
> Thanks,
> Dan Milon.
>
> [1] https://gist.github.com/**3029842 
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-**
> Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@**googlegroups.com
> For more options, visit this group at
> http://groups.google.com/**group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] Hook.io performance

[Dan Milon]

Hello,

I am using hook.io for some project.
Today i thought of measuring how fast hook.io can emit and receive 
messages, so i built a dead simple benchmark [1], and numbers are not 
that interesting.

It took 15 secs to deliver 10k messages from one hook to another.

I do not know the underlaying mechanisms hook.io uses for IPC (please 
enlighten me), but isn't this performance quite low? Or is there 
something wrong with the test?


Thanks,
Dan Milon.

[1] https://gist.github.com/3029842

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en