Re: Variables in Queuemonitor Objects

[Kedarnath Poduri <kpoduri@BayNetworks.COM>]

hi
	I don't think you are setting the packetSize_ variable correctly.
packetSize_ variable is already in Bytes. So if you set it to 1024 it
should have been 1024 bytes which it is not. So, CBR is generating packets
with default size of 210 bytes as your integrator computes and what is seen
in qmonitor until time 1. I can't say without looking your scripts why
after that qmonitor gives such an arbitrary result. If you set the
packetSize appropriately things should be fine.

kedar
>Hi, 
>
>My program monitors packets and bytes that have arrived 
>on a link using parrivals_ and barrivals_. 
>The result is (time, packets, bytes):
>
>0 0 0
>1 266 55860        #  1 packet = 210 bytes
>2 462 118184       #  1 packet = 255.** bytes
>3 741 180844       #  1 packet = 244.** bytes
>4 1007 243216
>5 1286 305876
>6 1537 368354
>7 1807 430752
>
>I set packetSize_ to be 1024 (TCP and CBR), 
>so 1 packet = 128 bytes. 
>
>Could anyone please explain why the result gets 
>different proportions?
>
>I used "queue-sample-timeout" in the same program and got  
>$meanBytesQ and $meanPktesQ, the values of Packets/Bytes
>were also variouse, which were around 200. It might understandable, 
>because it used integrator to do approximate computation, right?
>
>Thank you!
>
>--bc-
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++
>Bing Chen   (702)895-1428      bing@ee.unlv.edu 
>Dep. of Electrical and Computer Engineering
>University of Nevada, Las Vegas, NV  89154
>++++++++++++++++++++++++++++++++++++++++++++++++++++
>