Prashant,
After taking a look at your stats, I believe the problem here is that
the rails app is the culprit - it is doing more database work as rows
are added to the database as part of the run and consequently, the
longer you run, the performance will get worse. This does not a good
benchmark make.
We discovered one such problem in the PHP app - see OLIO-52. This was
caused by the fact that we were displaying the full list of attendees
for an event. As we add events and attendees during a run, each new
EventDetail operation would fetch more data causing more work to be
done. We have fixed this in the PHP app by limiting the number of
attendees retrieved to 20. Of course, the correct solution is to provide
paging so that a user can page thru the entire list if he wants - that
will have to wait for now.
Will - since you're the person most familiar with the rails app, can you
please figure out which operations are likely to be bitten by this
problem ? We'll have to work around ActiveRecord if need be to fix the
issue.
Shanti
On 02/25/09 10:50, Prashant Srinivasan wrote:
Hi,
I'm running the RoR version; MySQL CPU consumption seems to be
increasing over time. I'm running 20 minutes steady state . . . and
would expect the CPU time to have stabilized pretty quickly into the run.
Just sending this along to see if others have seen this issue.
thanks
-ps
