WARNING: This web is not used anymore. Please use PDBService.OracleRACLoadTestingInstall instead!



The framework is coupled to several tools available at CERN. You will need to check if everything is set up correctly.

  • Every client machine should have an AFS access. It allows us to distribute the code to the clients and gather the results in a single folder. NFS can be used as a substitute but it will cause problems for the web based report.

  • One of the client machines should be able to access all the other nodes via ssh and without password. This one will be used to start the manager script.

Source code

You can get the source code from the Persistency CVS :

cd ~/
cvs -d :pserver:anonymous@coral.cvs.cern.ch:/cvs/coral co -d PerfTests -P coral/Tests/Performance_RelationalAccess/

Web site configuration

A web site should be configured in order to publish the web based report. An AFS based is easily created using this page : https://www.cern.ch/WebServices/Services/CreateNewSite/ . Choose AFS folder for the Site type and put the log folder path (ie: /afs/cern.ch/user/j/jsmith/PerfTests/logs/).

Install JPGraph

Get it from there : http://www.aditus.nu/jpgraph/jpdownload.php ( use "PHP4: JpGraph 1.x - series" ) and put it in the log directory (as jpgraph) :

cd ~/PerfTests/logs/
wget http://hem.bredband.net/jpgraph/jpgraph-1.22.tar.gz -O /tmp/jpgraph.tar.gz
tar zxf /tmp/jpgraph.tar.gz
mv jpgraph* jpgraph

Access rights

Change the access privileges to the log directory to enable access from web :

fs setacl -dir ~/PerfTests/logs/ ~/PerfTests/logs/jpgraph/src/ ~/PerfTests/logs/jpgraph/src/lang/ -acl system:anyuser rl

Monitoring schema on the target database

You should create a specific schema on the monitored batabase to use the monitoring feature. A script called install.sql is provided in order to do so. You should execute it with a DBA account. You will be asked for a username and a password which will be needed by the framework afterward (in authentication.xml).

Framework configuration

Modify testConf.xml to configure the test environment.

  • Indicate the client machine and RAC node hostnames
<?xml version="1.0" ?>


  • you can enable or disable the different monitoring graphs (0 to disable)
        <statistic cpu="1" waitEvents="1"/>

  • you can set the "ramping-up" of the connections
  numCliNode="1"   -- number of machines used for this test run
  numSessPerCliNode="2"   -- total number of client programs which will be started on each client machine
  numSessIni="1"   -- number of client programs which will be started on each client machine at step 1
  numSessInc="1"   -- number of client programs which will be started on each client machine after each step
  stepDuration="20"   -- waiting time between each "ramping-up step"
  maxTestDuration="3600"   -- maximum duration of the test, after this period the clients are killed and the test is considered as finished

  • then you should indicate the folders used by the program
baseDir="/afs/cern.ch/user/j/jsmith/PerfTests/"   -- directory where you downloaded the framework
clientLogDir="/afs/cern.ch/user/j/jsmith/PerfTests/logs/"/>   -- directory where you plan to store all the log folders (if in another place, should remain on a shared filesystem)

  • you should specify the metric names you'll be using
  <dynamic>Object inserted</dynamic>   -- metrics which will be divided by the time taken to achieve the task here the meaningful value is a ratio (objects inserted / sec)
  <static>Memory usage in MB</static>   -- metrics which do not need calculation, meaningful as it is (MB)

  • here you should indicate the information related to the client program
      dbUser="ORACLE_USER"   -- name of the Oracle user which will be used as client for the test
      clientCmd="client.py"   -- command used to start the test program on the different client nodes
      clientExe="python"   -- test program real name as seen by the operating system (eg: python for a python script)
      reportPeriod="10"   -- waiting time between each monitoring output (also used in the client program to write results on this same frequency)
      reportDbConnect="/dbdev/OracleStress"    -- connection string used by the monitoring script (declared in dblookup.xml and authentication.xml)

  • and finally, you can save meaningful files in the log folder
 <file name="Client execution script">client.py</file>
   -- the client program should be saved in order to reproduce the test easily
 <file name="Configuration file">testConf.xml</file>
   -- a saved version of the configuration file is also needed 
      to generate the report

Database access

You'll have to modify the configuration files authentication.xml and dblookup.xml. They are needed by the monitoring extension and perhaps for the test client.

First the account for the monitoring
<?xml version="1.0" ?>
  <connection name="oracle://oracle_service_name/oracle_monitoring_username">
    <parameter name="user" value="oracle_monitoring_username" />
    <parameter name="password" value="oracle_monitoring_password" />
Then the account for the test client for each node (if using COOL or CORAL)
  <connection name="oracle://oracle_service_name_node1/oracle_client_username">
    <parameter name="user" value="oracle_client_username" />
    <parameter name="password" value="oracle_client_password" />

  <connection name="oracle://oracle_service_name_node2/oracle_client_username">
    <parameter name="user" value="oracle_client_username" />
    <parameter name="password" value="oracle_client_password" />

Persistency uses also this file to declare the monitoring service name
<?xml version="1.0" ?>
  <logicalservice name="/OracleStressReport">
     <service name="oracle://oracle_serice_name/oracle_monitoring_username" accessMode="readonly" authentication="password" />

Set the environment variables

There are two files provided depending on your shell. For bash, sh or zsh use bashrc and for csh or tcsh use cshrc.

You can copy them in your .bashrc (or .cshrc) or source them from there :

source ~/PerfTests/bin/bashrc

Don't forget to modify the following variable if needed :

export CMTCONFIG=slc4_amd64_gcc34  -- eg can be changed to slc4_ia32_gcc34 
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2010-06-11 - PeterJones
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    PSSGroup All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback