Re: How would you code an infinite RPG loop - Was 1 <> 1 is true???

Buck wrote:

Running a no-op loop to consume cycles will get you a 'doesn't play nice 
with others' grade, since this code will rapidly be consuming processor 
cycles that other jobs will want.  DLYJOB, or one of the C wait() 
functions will in essence set a timer and go to sleep, consuming no 
processor cycles until the timer goes off.

If the system is too slow to process the data queue and it is filling
up, then not using a delay/wait would be sort of like flogging a dead horse.

This is the first I've heard of where the data queue is hovering on
full.  But rather the coding for data queue full, it might make more
sense to fix the process on the other end.

Depending on how the application is designed, maybe multiple data queue
server jobs (the job receiving the data queue entries) can be used.
This can be a tunning technique (run more data queue servers when the
data queue process is the bottle neck).


Keith