On 11.02.2012 19:30, Tudor Girba wrote:
Hi,
Sorry for the late reply, and thanks everyone for the suggestions.
I did not provide much details because I am new to this domain and I wanted to see from the reactions if maybe I am not missing some relevant direction.
We are trying to measure how an Oracle database can cope with an increase in usage (basically, there will be more users for the application).
Just more users or also more data? Will the users access the database through one application or does each have it's own application?
We are basing our analysis on typical SQL statements coming from the application. We are currently doing load testing by: - recording sql statements from some use cases that are considered to be important - generalizing them by replacing actual values with generic variables
That shouldn't be necessary, the queries should already contain bind variables (unless your database layer is crap).
- providing meaningful values for the generic variables - replaying them against the database from several client machines - consuming the first record from the responses
Why only the first?
- reporting the timing of the statements - recording the CPU, memory and I/O load of the server
Oracle already provides tools for many of these things.
However, I am interested in pitfalls, and in the way people interpret the results given that it is hard to determine what is a typical usage in terms of what statements to trigger and at what delays.
The yourself a competent Oracle-DBA and probably sysadmin and storage guy as well. No seriously, you wouldn't want to have GemStone benchmarked by someone who has never used Smalltak before, would you? Cheers Philippe