Thanks Massimo, I hope it proves useful. We have close to 200 instances of various flavors of the same T4/T5 app with this profiler. One of the bigger ones has a db close to 400GB (data only, probably many TB of images/video as well). I'm not sure on the concurrency levels; these are private apps but there hundreds of pages and around 100 different quartz jobs on each instance. Our scalability challenges tend to be in the area of managing lots of data, rather than heavy concurrent usage, but I would expect the profiler should be general-purpose enough to handle both cases.
On Sat, Sep 8, 2012 at 3:48 AM, Massimo Lusetti <mluse...@gmail.com> wrote: > On Fri, Sep 7, 2012 at 11:52 PM, Ben Dotte <ben.do...@gmail.com> wrote: > > > Hopefully this will be useful to others; we have not seen any noticeable > > overhead and we have used it frequently on large, busy production > instances > > to track down issues that always seemed to elude us in the past. > > > > Comments or suggestions are welcome. > > I'm always interested in monitoring arguments I'll give a whirl to it > as soon as possible. > > Thanks Ben and Widen. > > BTW Would you mind to share what is for you a "large, busy production > instances" ? > > Cheers > -- > Massimo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
