Notes on Workload generation

In order to measure performance and categorize the workload if required, i have to know what is the type of workflow generated.

Now reading the paper for LCG and how the workload was collected.
Performance metric used : job turnaround times to rank resources after matchmaking.

Sample jobs from the LCG log
 1        0     -1     83    1     -1    -1   -1     -1    -1 -1   1   1  -1 -1  1 -1 -1
    2        3     -1   3611    1     -1    -1   -1     -1    -1 -1   2   2  -1 -1  2 -1 -1

• each workload is stored in a single ASCII file
• each job is represented in a single line.
• irrelevant fields are marked with -1

FIELDS

1. job number
2. submit time
3. wait time (sec)
4. run time (sec)
5. no. of allocated processors
6. avg CPU time use

But what i found out was when it is converting the log files and taking,
The job number as cloudlet ID, fourth field is stored as cloudLetTotalLength

Hiccups:

I don't know why after workload is generated all submission times are 0 whereas in the swf file variable submission times are given.

Tried to get the cloudlet information after workload submission
1
 History:No history is recorded for Cloudlet #1
 Status:Created
All resource ID's:null
Cloudlet FileSize:1
Finished so far:83
cloudlet Length:83
Op Size:1
cost per sec:0.0
start time:0.0
End time:-1.0
net service level:0
Pe's:1
proc cost:0.0
user id:-1
cpu utz model:org.cloudbus.cloudsim.UtilizationModelFull@b1cc87

I'm thinking its probably a bug 'cos start time never gets read anywhere....
So I wrote some code to submit each job after a 3 second delay.(If more datacenters are simulated, i could probably have jobs submitted at the same time to simulate simultaenity.
I segregated the output to by VM's

To be done:

write code in java to display chart for the output because now making any deductions from the log is difficult