Re: RE: RE: Re: [certi-dev] CERTI performance issue

[Eric Noulard]

2009/6/16 Gotthard, Petr <address@hidden>:
> Aaaaah! I have a plausible explanation: You do nextEventRequest() and then
> immediately check for the grant, which did not arrive yet. Then you wait 1s
> and check again. Although the grant doesn’t arrive immediately, it arrives
> very soon. But you always wait for 1s before the second tick(). The second
> tick() always succeeds.
>
> To prove my theory, you can use usleep(0.5 * 1000000) instead of sleep(1).
> This will wait only 0.5s. If I’m right, the performance will improve, but
> the TICK count stays the same.

Yes +1 for the analysis.

After you tried the Petr solution I would advise you to
add an usleep(5 * 1000)  BEFORE ticking the first time
(may be put before the while loop) this may leads you
to grantArrived with no further sleep most of the time, thus
you'll drop the number of tick too.

-- 
Erk