> That's a nice euphemism. I didn't check the code thoroughly, but rehashing
> seems to be O(n^2) in WeakKeyDictionary. This affects it's subclasses and
> WeakRegistry which affects the whole finalization process.
>
> (Recently I did a benchmark of Seaside 3.0, where Squeak handled 1.28x more
> requests/second than Pharo under "heavy load" (50 concurrent users flooding
> the server) with the Kom adaptor.)

Seaside doesn't use any weak data structures.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to