"Lahooti, Hamid" wrote:
>
> We have a real life web based application which has random loading by
> nature. Some clients query evaluation of their portfolios a few times a day
> while others want it a few times a year. We could have 10000 clients
> accessing the system all at once when interest rates are changed.
>
I wouldn't call this random at all. I see definite patterns in the use of the
beans. Of course, you could see it as random in a LARGE view, but the cache will
most likely include, say, a few hundred entities at a maximum, and thus the
localized pattern (within matters of minutes, hours or a day) will be the ones
that will benefit from the cache. The pattern for a year doesn't matter.
If interest rates change and you get the full 1000 clients accessing the system,
you will most likely get cache benefits for the entites that are affected by
this change. The use will be localized to a group of entites, and it will be
localized in time as well, since the entities will be used for a while, then
another set will be used etc. All entities in the system will not be used the
whole time during the 10000 client access period. IMHO
regards
/Kalle
--
In a Paris hotel elevator: "Please leave your values at the front desk."
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://travel.to/kp
Telephone: +46-(0)13-17 99 29
Cellular: +46-(0)739-87 11 03
ICQ: 4744258
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
