Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pcmaster]

Statistics in amulegui.

Please, don't say that this make high-bandwith use. If statistics are updated one time each second, isn't necessary to transfer all graphics each time.

Open the amule windows and see the statistics tab. If amulegui window is 1024 pixel width, each graphic is 445 pixel width. As this, the total statistics (the page it has 3 graphics) are 445x3=1335 pixels. This is: graphics shows 1335 values.

The statistics my be calculated by amuled, not amulegui. When amulegui starts, it may ask amuled for the statistics values. It can obtain 1335 bytes of info (one byte for value may be suficient, it can obtain more or less bytes according to amulegui windows size) and then shows the values. This makes initial data transfer of 1335 bytes.

Then if gaphics can be updated, for example, as a one new value each second, amulegui can scroll horizontaly fron right to left the graphics values and ask to amuled for athe new data: only 3 bytes of info, one for each graphic, in order to add new data al the right.

The numerical statistics at the right: it can be transmited once with the initial connection, adding the data to the initial 1335 bytes, and then, each second, send only the changes, adding the info to the 3 byte connection.

This is not a very high bandwith use.

[GonoszTopi]

Please do not post into unrelated threads, open a new one instead.

[Kry]

I think you're missing the point that the size of the graphics is client-dependant.

[pcmaster]

Hello, Kry,

Yes, the size of the graphics is client-dependant. Also a big windos shows more statistics data than a litle window.

But no problem. The client can ask amuled for the ammount of data it needs (it can transmit a "i want a 30 second of statistics data") and amuled transmit only the data amulegui has asked for.

The transmision is statistics-data-only, is amulegui, not amuled, the program that can convert it to graphics.

In otehr words: amuled can maintain always the statistics data, and amulegui ask for the needed data when is needed.

[lfroen]

Please, don't say that this make high-bandwith use.

That's depends on implementation. Now, how match is "high"? My "broadband" have upstream of 20KBps. Any application requiring more than 5Kbps considered "high bandwidth". Not everyone live in Japan.

If statistics are updated one time each second, isn't necessary to transfer all graphics each time.

There's actually 2 statements here: 1) update can be done each second sharp 2) only part of data is needed. You see, the #1 is false, meaning that you can't guarantee that each update will come exactly 1sec after previous one. That's depends on network conditions and load on daemon. This means, that while #2 is true, actual %% of data may vary.

If amulegui window is 1024 pixel width, each graphic is 445 pixel width. As this, the total statistics (the page it has 3 graphics) are 445x3=1335 pixels. This is: graphics shows 1335 values.

This calculation is wrong all over. Graph is not straight horizontal line, you know (if it was like this, only 2 values were needed). As a result, all later calculations wrong as well and not worth discussion.

But no problem. The client can ask amuled for the amount of data it needs(it can transmit a "i want a 30 second of statistics data")

Yes it can, but it's something that must be implemented this way.