Re: [PATCH] schedule connect timeouts via eventAdd

From: Rainer Weikusat <rweikusat_at_mobileactivedefense.com>
Date: Wed, 23 Jan 2013 23:39:48 +0000

Rainer Weikusat <rw_at_sapphire.mobileactivedefense.com> writes:

[...]

> The downside of this approach is that this means adding
> future connect timeouts will become proportionally more expensive as
> more and more connections are being established

This is an understatement. Based on a somewhat simplified model of the
event list (initially empty, only connect timeouts), adding n timeouts
in a row would have a cost cost 2 * (n - 1) + 1 (assuming 'insertion
cost/ empy list' 1, same for removal cost) when adding and removing
the events but would be (n * (n + 1)) / 2 for the other case (sum of
1 + 2 + ... + n).
Received on Wed Jan 23 2013 - 23:40:03 MST

This archive was generated by hypermail 2.2.0 : Thu Jan 24 2013 - 12:00:08 MST