Nifty! Thanks.

As far as your question about metrics goes:

On just one network, freenode being a larger network, right now I'm in channels with these populations. (Though I'm often popping in and out of different channels, some larger than others.)

[1960] [1267] [1243] [1039] [882] [851] [835] [795] [624] [588] [525] [506] [480] [475] [444] [425] [389] [371] [366] [348] [315] [309] [252] [251] [225] [225] [182] [173] [165] [155] [151] [148] [143] [143] [138] [121] [116] [113] [111] [109] [107] [107] [106] [102] [100] [89] [88] [87] [87] [86] [85] [82] [78] [76] [74] [68] [64] [60] [59] [50] [48] [48] [47] [47] [46] [46] [44] [40] [39] [39] [34] [31] [30] [25] [22] [22] [19] [18] [11] [7] == 20276

When there's a netsplit, I estimate at least 10 to 20% of those populations produce a quit message, which equates to about 2,000 to 4,000 quit messages being printed.

mIRC.exe usually idles around 2% ~ 6% for me, but peaks out at 50% (100% of a single core) for a fair period of time when there's a netsplit or re-join.

I know I can hide these event messages, but I do like to have access to them in my logs.


Well. At least I won lunch.
Good philosophy, see good in bad, I like!