]project-open[ : @This Wiki
Portrait

Welcome, Unregistered Visitor

Contents

User Profiles

10 registered users
 in last 24 hours

Timesheet Benchmark

This benchmark simulates the load that an employee will add to the system when logging hours on a project.

The benchmark consists of the following steps:

  • Log-on to the system
  • Load the "Home" page with the components:
    • Home Personal Open Projects Component
    • Home Forum Component
    • Home Workflow Component
    • Home Filestorage Component
  • Click on a random project in the "Home Personal Open Projects Component"
  • Load the "Project View Page" for that that project with the components:
    • Project Main Data
    • Project Hierarchy
    • Project Members
    • Project Timesheet Tasks
    • Project Timesheet Component
  • Click on the "Log your hours" link of the "Project Timesheet Component"
  • In the "Timesheet New Page" enter a random number from 0,5 - 2 in one random field and submit the form
  • Log out

The benchmark is part of the ]po[ distribution in /packages/intranet-core/benchmark/benchmark_timesheet.test.

To execute the test, please use the ]po[ version of TclWebTest available via CVS:
cvs -d :pserver:anonymous@cvs.project-open.net:/home/cvsroot/ checkout tclwebtest
Please see the README for installation instructions.


Benchmark Results


090518 Benchmark on a Consulting Test Server

Running the Timesheet Benchmark on a server typicial for a consulting company with about 200 projects and 1000 timesheet entries. This configuration corresponds to a mid-sized consulting company with about 20 in-house users working with ]po[ for 1.5 years.

Results:

  • 1 parallel benchmarks running: 199.7 ms per page (0 seconds delay)
  • 5 parallel benchmarks running: 432.8 ms per page (0 seconds delay)

 

090518 Benchmark on a Translation Test Server

Running the Timesheet Benchmark on a real-world Translation Testing System with more then 10.000 projects and 20.000 timesheet tasks. This configuration corresponds to a mid-sized translation company with about 20 in-house users working intensively with ]po[ for 3 years.

Results:

  • 1 parallel benchmarks running: 419.5 ms per page (0 seconds delay)
  • 5 parallel benchmarks running: 1210.2 ms per page (0 seconds delay)