From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Performance of many concurrent delay() calls
Date: Mon, 07 Nov 2016 22:30:24 +0100
Date: 2016-11-07T22:30:24+01:00 [thread overview]
Message-ID: <87twbj6kr3.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: 1a375eea-b087-4080-a492-62bc26a8123c@googlegroups.com
* Olivier Henley:
> Does calling [loop and delay(1.0)] for each of many thousand connected
> clients (gnoga/simple components) is a huge performance hit or not?
Periodic wakeups are considered bad for battery life and also
negatively impact density of VMs (and containers).
> If so, what is the recommended way to implement a periodic, every sec,
> procedure that has to run for every clients; instantiate a single main
> task looping, delay(1.0), over all connections data and call the
> wanted procedure... probably?
I think this depends on what has to be done every second, and to what
degree these actions depend on other resources.
next prev parent reply other threads:[~2016-11-07 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 18:52 Performance of many concurrent delay() calls Olivier Henley
2016-11-07 19:04 ` J-P. Rosen
2016-11-07 19:13 ` Olivier Henley
2016-11-07 20:57 ` Dmitry A. Kazakov
2016-11-07 21:30 ` Florian Weimer [this message]
2016-11-07 22:42 ` Jeffrey R. Carter
2016-11-09 15:50 ` Olivier Henley
2016-11-09 23:15 ` Jeffrey R. Carter
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox