Re: Deployment Configuration and limitations
Chuck Hill <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.admin |
|---|---|
| Message-ID | <[email protected]> |
On Mar 19, 2004, at 9:19 AM, Ute Hoffmann wrote: > Hi, > I have concurrent request handling enabled. Where is the limit of the > number of concurrent Sessions? You can set this on the command line, WOWorkerThreadCountMax I think. The default is 256. > There is still plenty of free memory on the machine, so would I be > able to have more sessions running on one instance if I increased the > memory of the JVM? > Yes. Memory is usually the limiting factor in the number of concurrent sessions that can be handled. > If I use concurrent request handling, can I still have more than one > instance of the same app running or would that be a bad idea? > That is fine too. Access is serialized at the EOF level so you won't get full multi-threading. Running multiple instances is a good idea. > What is a normal/average number of sessions a instance can handle > concurrently? > That depends on the amount of memory in the JVM, the average session usage of memory, and the amount of processing the app does. This number is very application and server dependent. Chuck > Thanks for some input, regards, > Ute > > _________________________________________________________________ > STOP MORE SPAM with the new MSN 8 and get 2 months FREE* > http://join.msn.com/?page=features/junkmail > > _______________________________________________ > WebObjects-admin mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/webobjects-admin