[Click] some outputs from peak rate measurement, and questions

[Eddie Kohler]

> Next are the handlers printed out by PokeHandlers, running at user-level. 
> It was called in this way: PokeHandlers(read ctr.rate, read ctr.count, 
> read ctr.byte_count, read myqueue.drops, write ctr.reset, wait 1, loop); I 
> assumed that ctr.count should be close to ctr.rate if not exactly the 
> same, since there's no drops of packets from the queue. Also, I thought 
> ctr.count should be the product of ctr.byte_count and size in byte per 
> packet. However, neither is the case as I expected, as you can see from 
> below: 
> 
> ctr.rate:
> 518795.996
> 
> ctr.count:
> 743040
> 
> ctr.byte_count:
> 40867200

The Counter.rate handler is implemented by an exponentially weighted moving 
average so it's not surprising it's off.

And you've got count and byte_count backwards: byte_count is the product of 
count and size in bytes per packet.

Eddie


> 
> myqueue.drops:
> 0
>     
> ... more repeated prints, but with similar values as the above for each 
> handler.
> 
> Anyone has any ideas/comments/suggestions? 
> 
> Thanks a lot,
> 
> Lan
> 
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click