Re: [Chromium-environment] n log n Startup Scalability

[Karl R. <rk...@vr...>]

> Regarding the problem of starting huge numbers of nodes (current code requires 
> all nodes to contact the mothership for configuration, and the mothership is a 
> single process that handles the connections linearly)...

I've probably joined in the middle of some thread, so ignore me if 
necessary...

What about caching config info on the server side? At least here I run the 
same config over and over again, switching between apps as people change 
their mind as to what they want to see..

This won't help any when you change nodes in a config or whatnot, but, 
maybe thats a different problem..