You are not logged in. Click here to log in.

codebeamer Application Lifecycle Management (ALM)

Search In Project

Search inClear

Tags:  not added yet

codeBeamer Performance Sanity Check

CodeBeamer is designed, implemented and tested for enterprise use.

Virus Scanners

Virus scanners running and scanning network and/or file systems used by codeBeamer (or the database files and/or partitions) might significantly impact codeBeamer's performance. Even virus scanners reported as installed but non-active can impact performance.

It is recommended not using virus scanners on codeBeamer host system.

Withe Oracle database you can store all data inclusive documents and Wikis in the Oracle database and when your virus scanners are not scanning the Oracle communication port, you can ovoid this performace degradation.

Network Shares (NFS)

Similar to Virus Scanner Network Shares can also significantly impact codeBeamer performance.

It is recommended installing and running codeBeamer on fast local disk.

Network Latency

If codeBeamer's database is hosted on a different machine, network availability determines generally codeBeamer's performance. Please measure (ping) and ensure fast and reliable connection between codeBeamer and the database host. Virus scanner might also scan network traffic!

Derby Database

codeBeamer is shipped with the Derby database for evaluation purposes. Derby is neither recommended nor supported for production, please refer System Requirements about supported databases.

Profiling Database Performance

If you want to tune your database server please read: MySQL server tuning

With steps below codeBeamer's database access performance can be measured:

  • Login to codeBeamer as system administrator
  • Click on iSQL link under System Admin Tab and click on Test Performance button.

The example below was created on an ubuntu-10.04, 64 bit 8 GB Quad-Core Processor system using mysql-5.5.23:

Profiling Request Processing Time

All requests, their execution time and some other important data is stored into log file <cb-installation-dir>/tomcat/logs/requests.txt.

2013-11-11 15:23:04,263 - Request-82233 84.3.193.217 2136 "GET /cb/issue/63886 HTTP/1.1" [29B8400626B183A1C8F72762705F1D7E] "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36" "https://codebeamer.com/cb/issue/41039" free(mb): 782 total(mb): 2135 max(mb): 2222 vm(mb): 3650 threads: 14/21 dbcons: 0/3

The example above shows how much resources (memory and database connections) were in use when a request (82233) arrived to codeBeamer (tomcat) and the example below describes how long it took to process the request (82233) and how much resources were in use after the request was processed.

2013-11-11 15:23:05,902 - Request-82233 elapsed: 639 ms. free(mb): 685 total(mb): 2135 max(mb): 2222 vm(mb): 3650 threads: 14/21 dbcons: 0/3

Performance Testing

Please refer Performance Tests how to execute performance testing.