Hi,


Seems possible and fine. Have you already run your programme at your scale 
? Did you profile it ? Are you using multiple nodejs processes ?


This might guide you : 
https://www.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/
.


Regards,

Sven

Le dimanche 18 septembre 2016 17:17:14 UTC+3:30, Alain Mouette a écrit :
>
> Hi,
>
> I have a problem to control a few thousand websocket connections, for that 
> I need a timer for each one...
>
> first option) on every event I create a *setTimeout()* and delete the 
> last one, once every 60s, 5000 timers, once every 12ms average.
> My QUESTION IS: will I have a big overhead for having all these timers? 
> and will I gar a lot of GC
>
> second option) create a single *setInterval()* for each connection that 
> will wake me up every 30s and I just check if everyting is ok.
> My QUESTION IS: will I have a big overhead for having all these timers? I 
> surely will get less garbage, right?
>
> Any different suggestion?
>
> Please help,
>
> Alain, from Brazil
>
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/9b8593fd-0323-400d-9d02-391b2006c0b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to