What memory/CPU resource is required for a modest BuildForge Implementation
I wish to control about 15 separate test machines (Linux/AIX) from a single Build Forge server. Each test machine will run a simple, perl based test script, but may generate several MBytes of log data. I'm told I need a server with 48G of RAM, but the manuals say I need 2G !
What are people's experience? how much server RAM is needed for the management console? (At the moment when I run reports I see the console hang - I have 8G already - and also it make take some time (10s of seconds) to initially login to the server console. Is this application really so memory hungry - and if so, why ? many thanks |
One answer
Capacity planning with BF is a very open ended issue. It sounds like a non-answer, but the capacity depends on how much you're asking each running job to do.
WRT memory, each running job creates a new process requiring some memory. It usually starts out at a few MB, but will grow with time depending on how much data it's moving, and other things it's doing. The engine itself (the bits that spawn new jobs) will require some memory, the services layer (the glue that holds it all together) will need about one GB typically, and the apache/PHP side of things will take some too. All of that is pretty variable depending on load except for the services layer. It is pretty consistent topping out at a gig, more if you've configured it as such, but that's atypical.
Who told you 48GB and under what context? Was that to run one project at a time that runs one step on each of your servers collecting several MB of data? Or was that 48GB including the DB server, many projects running concurrently, and with many steps each containing several MB?
Typically, no. BF is not horribly memory hungry. But it can be depending on what you're trying to do with it.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.