Author Topic: How to debug an individual SPECvirt workload  (Read 720 times)


  • Moderator
  • Newbie
  • *****
  • Posts: 3
  • Karma: +3/-0
How to debug an individual SPECvirt workload
« on: July 04, 2014, 05:55:10 PM »
When setting up SPECvirt in a new environment, its sometimes helpful to get individual workloads running by themselves to debug any issues before running the entire set of workloads in a tile.

To make this easier, I created a symbolic Control.config (Control.config.v79.wkld) and used it to create a set of  Control.config files where the first workload in the tile is a different one of the workloads.  So now if you want to just run the web server workload or just the batch workload, etc you can select the appropriately named Control.config.v79.<name>1 file included in the attached .tgz file.  Or you can start with the Control.config.v79.wkld file and follow the directions in the comments to put the workloads in any order.  You'll also need to make the appropriate changes to the file for things like your client naming convention.    Note the results generated will NOT be compliant due to the order change but you'll be able to tell if the workload(s) you ran completed successfully or not.

tar -ztvf SingleWkld-Control.configs.tgz
-rw-r--r--  0 root   root    24249 Jul  4 17:25 Control.config.v79.app1
-rw-r--r--  0 root   root    24250 Jul 15  2013 Control.config.v79.batch1
-rw-r--r--  0 root   root    24346 Jul 15  2013 Control.config.v79.mail1
-rw-r--r--  0 root   root    24249 Jul 15  2013 Control.config.v79.web1
-rw-r--r--  0 root   root    24622 Jul 15  2013 Control.config.v79.wkld