work on sept 23

Plan
1) compare response time given by autoperf and httperf with no of users =1 for both view entry and write entry
2) check if we can measure the response time for Login transactions, problem was it wasn't calling week.php, if we do login
3) Finally do measure response time for viewEntrybyWeek transaction and write Entry transaction, login using httperf and autoperf.(p 1hour)
4) check out how service demand is being calculated for database server in autoperf. i.e why service demand went on increased (p3 hours )
5)check out tracers for both php and autoperf(p1 hour)
*
1) There was a problem that httperf output had 4XX=20. the problem was with input scripts written by me.
Httperf results with 1 req/sec is 108.8 ms
autoperf results with 1 req/s is 156 ms keeping thinktime 0.85 ms and utilization of webserver is 14 % and utilization of database is 0.97 % based on sar. but autoperf shows 14% and 0 % may be it cannot capture at this level
*autoperf results with 1 req/s is 165 at think time 1s
2) login.php , mistake done was assuming that ${y} generated in a particular transaction is constant. It is working, so we have three transactions login, viewentry, addentry on which i can measure performance.
3)I can do it so I will finish it off tonight and check results
4)
additional points:
I think, measurement of service demand at mysql from autoperf is wrong, so i am planning to measure the performance by writing some sample PHP which has all the sql queries in it. so it is similar to normal viewentry.
5)i may have to work on eclipse for autoperf, but what about tracer on autoperf-linux profiler and there are php debuggers

worked for 3 1/2 hours

started working from 9 in the evening..
Ran for login scenario on autoperf