View source | Discuss this page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Add page
Show collection (0 pages)
Collections help


Release Management/ERP sizing



A sizing is an approximation of the hardware resources required to support a specific software implementation, in this case Openbravo ERP. This document set the first foundations towards sizing the hardware required to run Openbravo ERP based on certain defined conditions.

General steps



Define the hardware to be used in Openbravo ERP based on certain information provided by the end user.


How precise do we want to be?



The goal is to prepare the most effective questions as possible. Type of information to be covered:


Gather real data

We already have many users around the world using Openbravo ERP, and we have the Heartbeat that provides information for some of these installations. Additionally the support team has information about real installations, which we can use to feed our database and tweak the final results.

Define test plan

The goal is to first define the different ways in which the resources are used through the application. So we need to first defined a set of workflows, with 3 different user profiles, based on the complexity of their usage:

We will ask the QA and the Platform Teams to help us writing these workflows.

Also, we need to define what the expected speed/delay is. As a general rule any page should not take more than 3 seconds to load. This parameter must also be measured against the available network bandwidth.

Create the measuring tool tests

We have chosen Apache JMeter as the performance measuring tool. The goal of this step is to translate the workflows into JMeter tests.

Define hardware environments

We will use Amazon EC2 as the base to choose the machines, using the following combinations and parameters:

And also the client side requirements.

Other factors:

Set up environments and run tests

The goal is to follow and run the tests using our tool and build a database out of this measurements. By creating a matrix of the hardware parameters vs the user requirements.

Important factors:

Performance benchmark analysis

The goal is to interpret the collected data and translate it into real requirements: CPU, Memory, Disk, etc.

Create sizing guide

The goal is to create the questionnaire and the possible hardware recommendations based on those answers.

Verify/validate the results

Do a real world test, verify that it is working fine. Tweak the parameters if required. Also verify with the Support team and the Heartbeat data.

Publish the results

It's time to deliver it to the community, customers and the sales team. It's important to choose the way in which the results are showed.

Retrieved from ""

This page has been accessed 513 times. This page was last modified on 19 February 2010, at 06:27. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.