On Martedì, set 16, 2003, at 11:35 Europe/Rome, Simon Urbanek wrote:
On Tuesday, September 16, 2003, at 10:24 AM, Stefano Iacus wrote:
It seems that RAqua consumes too much cpu time when doing nothing.
I can't see exactly why this is happening. We have few days to fix this up. Any idea (after having look at the code) would be fine.
Well, it happens exactly what the code says ;). RAqua is spending all the time in those loops like this one:
while(!InputFinished & !HaveBigBuffer) Raqua_ProcessEvents();
(This one comes from Raqua_ReadConsole)
Since in Raqua_ProcessEvents you simply call ReceiveNextEvent with kEventDurationNoWait, the function returns almost immediately and is called again ... so in effect you are hogging 100% CPU. I'd suggest using either some sensible timeout or kEventDurationForever.
yes, kEventDurationForever is only a partial solution as all the timers I have setup to refresh the console etc won't work.
Is there any way to let the timer wake-up ReceiveNextEvent when kEventDurationForever is set? This will be the solution.
stefano
Cheers, Simon
--- Simon Urbanek Department of computer oriented statistics and data analysis Universitätsstr. 14 86135 Augsburg Germany
Tel: +49-821-598-2236 Fax: +49-821-598-2280
[EMAIL PROTECTED] http://simon.urbanek.info
______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
