View Single Post
  #1   Spotlight this post!  
Unread 09-08-2012, 12:52
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,011
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
realtime runtime code throughput margin monitoring


I'm wondering how many teams add runtime throughput and scheduling monitoring in each thread (or parallel loop) of their practice or even competition deployed code.

Something like the following
Code:
* thread start *
t0=system_microseconds();
if (t0-t1)>TBD1 err1++; //scheduling monitor
t1=t0;
* put thread code here *
if (system_microseconds()-t0)>TBD2 err2++; //thread throughput margin monitor
* thread end *
"err1" and 'err2" could be displayed on the dashboard for each thread.