[GridSim-users] Timing question

[Alexandre S. <al...@im...>]

Dear GridSim users,

one of my colleagues is using GridSim. She is developing a specific 
broker and has obtained good results so far.
Thanks the development team for GridSim, by the bay...

We have now, however, a problem because we want use real numbers.

In some points we can define channel baud rates, MIPS, and so far... We 
assumed first that the base time unit was "seconds" based on some 
comments in the Example codes.
B
rowsing SimJava and GridSim documentation we have noticed slightly 
different references regarding time: (abstract) "time units", seconds 
and miliseconds as references.

Here is the problem: in some points we have to define delays:

In the line bellow, we are delaying 20 seconds? 20 milliseconds? or 
simply 20 time units?
super.gridSimHold(20);

In the line bellow, the event engine will delay 60*60 seconds before 
queuing the event or 60 minutes?
super.send(get_id(), 60.0*60.0, GridSimTags.BROKER_TICK);

These delays have to be consistent with the other parameteres (baud 
rate, processor MIPS) and this with the size of a "Gridlet to be 
executed in a GridResource (unit: in MI)"... That is, if the base time 
is an abstract time unit, how the time-dependant parameter are coherent? 
I am assuming that all time is based on the SimGrid time base (obtained 
by the clock() method).

Cold any one give us a hint?

Another question. Our broker needs to cancel a Gridlet (actually we 
cancel it in the Resource but our broker maintains a reference to it and 
resume it afterwards sending it again to the Resource ...). We have two 
ways to do this:

we can invoke a method on the AllocationPolicy object attached to the 
Resource or we can send an event asking this.
Ex.: super.scheduler_.gridletCancel(gridletSuspensoID, 
gridletSuspensoUserID);

Question, the difference is only the transporting mechanism, the 
cancellation method is the same, isnt it? And, the cancellation actually 
purges the Gridlet from the Resource? And how about the execution time 
registered in the Gridlet? What happens? There is an inclusion in the 
Gridlet code which deals with this problem (but was coded considering 
the Gridled wouldnt "leave" the Resource... our case is a little bit 
different.

Best regards,
-- Alexandre Sztajnberg