You can make the hard-limit very high; it can never exceed the number of request-processing threads configured for your servlet container. That, of course, brings into question why you would even need a hard limit (this may be over-engineered!).
I expect that in a later release, probably 5.2, you'll be able to configure these on a per-page basis. Manipulating the soft-limit and soft-wait I think will be very useful. On Thu, Apr 9, 2009 at 7:13 AM, Peter Kanze <peterka...@gmail.com> wrote: > Hello > > The default for the absolute maximum number of page instances is 20. > > Does this mean 20 users can request the same page at the same time? I am > rebuilding a website that has at peaktimes around 100 users per second, > requesting the same page (home page).. > > Should I then maximize the page-pool.hard-limit to 150? > > Is that an acceptable number, or do I get a big chances on permgen / > heapspace errors? > > What are acceptable values for page-pool.hard-limit, page-pool.soft-limit > and page-pool.soft-wait for high traffic websites? > > thanks! > Peter > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
