#20 Write stats collecting mechanism

zavřený
otevřeno před 4 roky uživatelem yannweb · 2 komentářů
yannweb okomentoval před 4 roky

Nedd #24

Find a way to collect stats in pool_handling process.

The collection mechanism should give access to UDP server ( see #19 ) to following data :

  • worker count
  • requests count last 10/5/1 minute
  • request time average (maybe ?) => slow IPC between worker & pool ?
  • total request counter (maybe ?) => will overflow ?!
  • idle/busy state (maybe ?) => change too fast ?
  • idle/busy ratio or workload (maybe ?)

We have to take care of not slowing down the workers with this component…

Maybe the collection child could help implementing this mechanism ?

__Nedd #24__ Find a way to collect stats in pool_handling process. The collection mechanism should give access to UDP server ( see #19 ) to following data : - worker count - requests count last 10/5/1 minute - request time average (maybe ?) => slow IPC between worker & pool ? - total request counter (maybe ?) => will overflow ?! - idle/busy state (maybe ?) => change too fast ? - idle/busy ratio or workload (maybe ?) We have to take care of not slowing down the workers with this component... Maybe the collection child could help implementing this mechanism ?
yannweb added this to the BETA version milestone před 4 roky
yannweb added the
enhancement
label před 4 roky
yannweb added the
_core
label před 4 roky
yannweb okomentoval před 4 roky
Vlastník

A solution to a fast request counter implementation can use semaphores :

When a worker starts handling a request it increment a sempahore. Meanwhile, a counter process (pool_handler or stats collection child) will attempt to decrease (fast enough) the semaphore with WNOHANG.

If the decrement semop do not fail, a counter can be incremented.

Note : the 10/5/1 min counters implies to store all requests timestamps ?? Maybe we can associate a timestamp with a request count ?

=> if 100 req/s stores {time(NULL), 100} and not time_t [100] = {time(NULL), time(NULL), etc.}

A solution to a fast request counter implementation can use semaphores : When a worker starts handling a request it increment a sempahore. Meanwhile, a counter process (pool_handler or stats collection child) will attempt to decrease (fast enough) the semaphore with WNOHANG. If the decrement semop do not fail, a counter can be incremented. Note : the 10/5/1 min counters implies to store all requests timestamps ?? Maybe we can associate a timestamp with a request count ? <code>=> if 100 req/s stores {time(NULL), 100} and not time_t [100] = {time(NULL), time(NULL), etc.}</code>
yannweb started working před 4 roky
yannweb stopped working před 4 roky
54min 36s
yannweb started working před 4 roky
yannweb stopped working před 4 roky
3h 12min
yannweb self-assigned this před 4 roky
yannweb added spent time před 4 roky
1h
yannweb added a new dependency před 4 roky
yannweb started working před 4 roky
yannweb stopped working před 4 roky
31min 16s
yannweb okomentoval před 4 roky
Vlastník

closed by b3af92459e

closed by b3af92459e
Přihlašte se pro zapojení do konverzace.
Loading…
Zrušit
Uložit
Není zde žádný obsah.