Finally I have the correct log. I think there is a bug in the standard workload format reader in cloudsim.... it just never reads the fields correctly.
Couldn't figure out how to read the SWF file in java... so I've read it using perl script.
Then, took only the needed fields
Hopefully now the simulation will run correctly.
I also had another doubt... the generateWorkflow() method assigns the run time of the cloudlet to the the cloudletLength ( which according to defn is No. of instructions in MI ).
I came across this post from Rodrigo who is one of the developers of cloudsim...
So now i'm just going to assign run time/ Execution time to cloudlet length... cos its just a simulator...
Later when I'm running this in Eucalyptus or something, i'll use RuBIS application or something like that...
On another note...
found another simulator which extends cloudsim called the workflowSimulator.
This simulate clusters jobs as tasks and submits them...
May be of use somewhere along the line.
Couldn't figure out how to read the SWF file in java... so I've read it using perl script.
Then, took only the needed fields
- Job ID
- Submit Time
- Wait Time ( Not Applicable when submitting workloads )
- Run Time
- No. of Processors
- User ID
- Group ID
- Partition ID
Hopefully now the simulation will run correctly.
I also had another doubt... the generateWorkflow() method assigns the run time of the cloudlet to the the cloudletLength ( which according to defn is No. of instructions in MI ).
I came across this post from Rodrigo who is one of the developers of cloudsim...
So now i'm just going to assign run time/ Execution time to cloudlet length... cos its just a simulator...
Later when I'm running this in Eucalyptus or something, i'll use RuBIS application or something like that...
On another note...
found another simulator which extends cloudsim called the workflowSimulator.
This simulate clusters jobs as tasks and submits them...
May be of use somewhere along the line.

No comments:
Post a Comment