I use the OrderdMap (to guarantee order). Since I am doing client side Java, performance is a non issue. Each user ("session") has it's own VM and own CPU.

On the server side, I use sticky session replicate nothing "design". So 6 app (SoA) servers each have their own cache (of their user's queries). The CPU is far from the bottleneck, it hardly budges. ( the 1st thing that maxes out is the dual gigabit NICs. Next is SQL DB server. Map splits... I wish I get to that as a problem. In any case, number of columns on a table is few).

.V

Clinton Begin wrote:

If I recall correctly, commons-collections fast Map implementations
are only better for reading, and could possibly be even slower for
writing.  This also complicates design because you have to find a
convenient place to set the Map to "fast mode".

Cheers,
Clinton




On Thu, 16 Dec 2004 14:18:09 -0600, Vic Cekvenich <[EMAIL PROTECTED]> wrote:


Also... I use Apche commons-collections.

.V









--
RiA-SoA w/JDNC <http://www.SandraSF.com> forums
blog <http://www.sandrasf.com/adminBlog>

Reply via email to