Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

General Information

  • Start Time: 10/23/2007 4:26:35 PM
  • Users: 100
  • Test Duration: 01:16:05

App server config

  • maxThreads=250
  • minSpareThreads=25
  • maxSpareThreads=75

Database Notes

  • Load Average: 0.07 to 6.21
  • Sar data for time in question(recorded on bricker)
    
    04:50:04 PM   runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
    04:20:01 PM         0       386      0.23      0.54      1.17
    04:30:02 PM         5       388      1.73      0.80      0.89
    04:40:01 PM         0       392      2.02      2.60      2.01
    04:50:04 PM         2       491      0.76      1.22      1.62
    05:00:01 PM         1       490      0.80      0.90      1.29
    05:10:01 PM         0       487      0.58      0.90      1.12
    05:20:01 PM         0       489      0.51      0.74      0.93
    05:30:02 PM         2       489      0.16      0.31      0.60
    05:40:01 PM         0       488      0.17      0.36      0.51
    05:50:01 PM         0       487      0.00      0.07      0.27
    

Silk Data

Note: This table is the concatenation of two tables from silk performer.  Therefore blank columns only mean the column didn't exist in the original table.

Stat

Count

Per Second

Per Minute

Per Hour

Average

Min

Max

Count

StdDev

Transactions

429

0.10

5.72

343

 

 

 

 

 

Requests sent

52,948

11.77

705.97

42,358

 

 

 

 

 

Overall Response Time - Page Time[s]

 

 

 

 

14.907

0.020

588.675

7,924

56.253

Conclusions

We conclude that load test and system configuration simulated the poor performance we saw in production with the views.

  • No labels