> just a thought i had while wandering around siggraph -- perhaps these
> "slowdowns" are not network related at all, and are simply the java
> garbage collector kicking in.
hmmmm indeed ;^}
what puzzles me is
it consistently happens
when >= 12 or so users are logged on
and consistently *doesn't* happen
whe <= 10 users are logged on
> if so, one way to avoid them would be to use a "bucket" allocator that
> recycles messages, instead of leaving it to the JVM to clean them up.
ahhh
this is an interesting idea ;^}
something like what a DB connection manager might do
to reuse a Connection object
after the using-class is done with the DB query...
make msg "blank" and make msg avail for reuse
after orig-user's message is sent?
sort of a heap for messages?
jeffs
--
Jeff Sonstein
Assistant Professor of Information Technology
Rochester Institute of Technology
---------------------------------------------
http://ariadne.iz.net/
http://www.it.rit.edu/~jxs/
http://ariadne.iz.net/~jeffs/jeffs.asc
=============================================
there are no bugs
there are just undocumented features
