PROOF TEST PLAN

1
PROOF TEST PLAN
2
The plans

• The goal of this test is to find an optimized
  hardware and software solution for a PROOF pool.
• Firstly, we will re-run all the tests we have
  done with the newest Root version in a more
  official way. The results of the tests should
  be more acceptable and trustable for people.
• We will get a better understanding of the PROOF
  performance with single disk and RAID system.
• We will get a better understanding of the
  performance for each Packetizer under different
  test environment. (I/O intensive or CPU
  intensive.)
• We will get a better understanding of the
  scalability of Proof Sessions with respect of
  various complexities of analysis code.
• The system optimization for multiple users
  access.
• Setup a web interface to publish the results.

3
Hardware Preparation

• We will still use 3 PROOF pools for different
  test purposes.
• Big pool
• 1 Redirector 86 computers
• 47 AMD 4x2.0GHz cores, 4GB memory
• 39 Pentium4 2x2.8GHz, 2GB memory
• We use just the local disk for performance
  tests.
• Small pool A
• 1 Redirector 3 computers
• 2 machines with 4 x AMD 2.0GHz cores, 4GB
  memory, 70GB disk.
• 1 with 4x Intel 2.4GHz core, 4GB memory, 2x
  400GB data disks.
• Default we have 8 workers running on each node.
• Small pool B
• 1 Redirector 3 computers
• 2 machines with 8 x Intel 2.66GHz cores, 8GB
  memory, 8x750GB on RAID 5
• 1 with 8 x Intel 2.66GHz cores, 8GB memory,
  24x750GB on RAID 5
• Default we have 8 workers running on each node,
  mainly for high performance tests.

4
Software Preparation

• We will setup following software environment for
  these 3 pools.
• Big pool
• 32bit SLC4.5 5.17.02 CVS ROOT for 32bit
• 1 Redirector 1 Supervisor 84 nodes
• 8 workers on those 47 4-core machines
• 4 workers on those 39 dual-core machines
• We use just the local disk for performance
  tests.
• Small pool A
• 1 Redirector 2 computers
• 32bit SLC4.5 5.17.02 CVS ROOT for 32bit
• Default we have 8 workers running on each node.
• Small pool B
• 1 Redirector 2 computers
• 8 x Intel 2.66GHz cores, 8GB memory, 8x750GB on
  RAID 5
• Default we have 8 workers running on each node,
  mainly for high performance tests.

5
Data File Preparation

• We are planning to put following data to the
  pools.
• Data from Wisconsin Group
• The CBNT root files we used before.
• Some new root files with different formats.
• PDP files (If we can get from ATLAS).
• Root files BNL people was using.
• Data from the PROOF Team (Proofbench)
• The root files which PROOF team thinks good for
  performance tests.
• The analysis code for these root files.
• The size of the datasets
• Small datasets. (lt 100 files)
• Medium datasets. ( 100 300 files)
• Large datasets. ( 300 1000 files )
• Huge datasets. ( gt 1000 files)

6
PROOF Tests on the Big pool

• The major tests we will make
• PROOF tests with different Packetizers and also
  with different types of root files.
• Performance tests with multiple users.
• Performance tests on undedicated pool.
• We let all the machines CPU be fully occupied
  by full simulation jobs and start PROOF tests on
  them to see how much performance dropped.
• We will also try to reserve one CPU core for
  PROOF and see how it goes.

7
PROOF Tests on small pool A

• The major tests we will make
• PROOF tests with different Packetizers and also
  with different types of root files.
• Scalability tests with multi-workers.
• Simple/Complex PROOF job tests.
• Better CPU/Memory load monitoring system.

8
PROOF Tests on small pool B

• The major tests we will make
• PROOF tests with different Packetizers and also
  with different types of root files.
• Scalability tests with multi-workers on single
  node or multi nodes.
• Simple/Complex PROOF job tests on RAID and
  single disk.
• Better CPU/Memory load monitoring system.