I've been known to set the TTL values low (say, 1 minute) and use JMeter or similar to set up a fleet of zombie web browsers. It'll give you all the stats of average response time, responses per second, etc.
As far as pound debugging I usually do the low-tech "add printfs to the code" approach. :) Joe > -----Original Message----- > From: Steven van der Vegt [mailto:[email protected]] > Sent: Thursday, December 23, 2010 11:24 AM > To: [email protected] > Subject: [Pound Mailing List] RE: Website stalls every 60 seconds > > Since this problem is of somewhat a priority to us, I started to > implement the delete-at-once functionality. It works, but I still need > to implement read/write locks because during the execution of the > doall() method we can't afford an insert. > > Do you guys have a good testing method? > > I'm looking forward to your opinions about this solution. If I'm not > responding to email the next few days, that's because I'm busy cooking > and celebrating Christmas :-) > > Steven -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
