[OpenSTA-devel] [ opensta-Bugs-908959 ] Compilation of large scripts can effect start time

[SourceForge.net <no...@so...>]

Bugs item #908959, was opened at 2004-03-03 05:47
Message generated for change (Comment added) made by dansut
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=908959&group_id=10857

>Category: Architecture
Group: Inconvenience
Status: Open
>Resolution: Accepted
>Priority: 2
Submitted By: Marc MAZAS (mmazas)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Compilation of large scripts can effect start time

Initial Comment:
When one has a big script that takes long to compile 
and initialize (eg 10-20 secs), and performs a test with 
VUs started in batch mode (eg every 15 secs), the "real" 
starts of the 1st VUs are delayed and the interval 
between them are not the same : example :

"Test Audit Log" shows :
17:57:30 : "Test Manager Initialized"
...
17:57:49 : first log for VU 1-1 (should have started at 
57:30)
...
17:57:49 : first log for VU 1-2 (should have started at 
57:30 + 15 = 57:45)
...
17:58:00 : first log for VU 1-3 (has started at 57:30 + 2 
* 15)

The issue is that the first 2 VUs perform the same script 
at the same time, which I want to avoid (eg to prevent 
deadlocks, side effects, ...)

----------------------------------------------------------------------

>Comment By: Daniel Sutcliffe (dansut)
Date: 2004-10-13 17:06

Message:
Logged In: YES 
user_id=19748

This is could certainly be an issue if you don't know about
it.  But if you care about deadlocks in certain pieces of
code replay then you should really be making use of MUTEXes
and/or SEMAPHOREs.

This is one where if there's an easy fix it will get done,
otherwise this error will just hang around as a warning to
others.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=908959&group_id=10857