Excerpts from William Morgan's message of Mon Jun 08 14:00:23 -0400 2009: > It's definitely worse than O(n). Loading threads could be sped up > dramatically by storing the thread structure somewhere (either cached or > just for every thread), since Sup does a lot of extra work rethreading > everything every time you start it up. FWIW I'm doing this the right way > in Sup 2.0.
I'm thinking about how to do this, and one of the first I'm blockers I'm running against is that it's not quite obvious what's invoking the thread building code thread.rb. As for caching the thread, I'm thinking of generating a unique ID for each thread and sticking that on every message. Whether or not this will actually help depends a lot on what the answer to the above question is. Cheers, Edward _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
