There's more than one way to do things | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
We've been using Devel::NYTProf::Apache for analysing the main application, so I can have a go at that. In the meantime I stripped out everything except the lines:
And it was still giving 1700ms per request - suggesting that its not the DB access at all... The SELECT difference was a cut and paste error, the scripts on the server do both have the WHERE clause. In reply to Re^2: mod_perl vs php performance when accessing Oracle under load
by amasidlover
|
|