<< Back to previous view

[QB-1364] Quickbuild max load
Created: 04/Sep/12  Updated: 27/Dec/12

Status: Resolved
Project: QuickBuild
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Siim Käba Assigned To: Robin Shen
Resolution: Fixed Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown
Environment: HP DL385G7 LFF CTO Chassis

cpu 1 HP 6174 DL385G7 FIO Kit
cpu 1 HP 6174 DL385G7 Kit
mem 16 HP 8GB 2Rx4 PC3L-10600R-9 Kit
cache 1 HP 1G Flash Backed Cache
disk 6 HP 600GB 6G SAS 15K LFF (3.5-inch) DP ENT HDD
---
kernel 2.6.32-5-amd64
---
mysql 5.1.61-0+squeeze1, sun-java6-jdk 6.26-0squeeze1, -XX:+UseConcMarkSweepGC -Xms2048m -Xmx6144m -Xss512k -XX:MaxPermSize=512m


 Description   
We have around 13 400 configurations and 570 000 builds.

What is the max load (expressed in configuration counts, build counts, queue length, builds waiting for resources or any your chosen metrics) for QB SERVER?
What is the average response time QB UI must response with?

We have a lag with Server UI and would like to know where are the QB limits what you still support or think that are the cases for bug reports?

 Comments   
Comment by Robin Shen [ 05/Sep/12 12:44 AM ]
It is hard to tell a limit for build server since it highly depends on how frequently you scheduled the build, and how heavy the build itself is (even if build steps are dispatched to agents, build logs and artifacts still need to be transferred back to server, and artifacts of dependent builds also need to be transferred to agents).

So instead of guessing the load, we'd like to check why the UI is slaggish. Firstable, please make sure that all your builds are set to run on agents instead of server (this can be done by dispatching master step of the build to agent), then please turn off auto-refresh of the UI (by specifying auto refresh interval as 0 in system setting).

Also is the UI always slaggish or is it happening occasionally?
Comment by Siim Käba [ 07/Sep/12 11:06 AM ]
There probably isn't any query for that and clicking thru 13400 confs isn't a option, when its changing and someone can change it any time. But, can the log be improved so that it would log conf id - step - agent id?
Comment by Robin Shen [ 08/Sep/12 01:02 AM ]
The system log already shows where the step for certain configuration is running. Or you can write a script looping all configurations to check its step node match setting. Also please make sure to upgrade to latest QB version as it solves a problem of UI sluggish when some problematic agent is connecting to QB server.
Comment by Robin Shen [ 27/Dec/12 12:16 PM ]
Latest version improved the UI a lot for large number of configurations and builds.
Generated at Thu Jun 13 15:23:10 UTC 2024 using JIRA 189.