From: Ian Sparks <Ian.Sparks@et...> - 2003-10-22 22:03:09
I'm planning on using the ExtraUrlPath information to provide a lot of =
services out of a single servlet.
So instead of a swarm of small servlet instances I'll have a small pool =
of very fat servlets.
I'm wondering what implications this has for performance, scalability =
In order to handle a large concurrent load I'll probably need to enlarge =
my servlet pool - that has some memory implications but there should =
only need to be one copy of the servlet code in memory so the memory =
requirements are all about the data the servlet loads up and shunts =
Importing a lot of packages won't be a problem if done under a =
lazy-loading scheme that only loads them when needed - so the servlet =
startup time shouldn't be a big issue.
So what else am I missing? If there's a big roadblock ahead I'd rather =
know sooner than later.
Ian Sparks wrote/napsal:
: Importing a lot of packages won't be a problem if done under
: a lazy-loading scheme that only loads them when needed - so the servlet
: startup time shouldn't be a big issue..
: So what else am I missing? If there's a big roadblock ahead I'd rather
: know sooner than later..
I was testing my WebKit application for high concurrency on my
notebook and it looked to behave normal to me. There can be problem with
old servlets, as I didn't tested it. (I have to go home from work, so
I turned the Webware and notebook off). I don't know the way how the
servlets are relased.
Have a nice day
Věroš Kaplan <veros @ tac . cz>
Tacoma Computers, Staňkova 18a, Brno, CZ
"All parts should go together without forcing. You must remember that
the parts you are reassembling were disassembled by you. Therefore,
if you can't get them together again, there must be a reason.
By all means, do not use a hammer."
-- IBM maintenance manual, 1925