This may be suited to the Applications forum more but since I'm trying to measure something regarding a thin client + server network...
I'm trying to measure the relative performance of different encoding schemes across different network speeds and packet loss. One of the main ideas of measurement I have is measuring the time it takes for the following to happen:
1. Press enter on the thin client which sends data to the server and the server starts an MRI viewing application
2. Server then does all the processing work and sends the screen image data back in a preselected encoding scheme
3. The client "unpacks" the data and fully loads the image
So basically, the time it takes from the time you hit "go" to the time the image is loaded on the *client* side.
I have some ideas I'm looking into with for the "go" timestamp, ranging from just trying to timestamp on the client or timestamping when the server receives the message (and subtract off the latency and compensate for different internal times potentially), but I'm feeling stumped about how to track when the MRI image "loads" (I say "loads" because it's not a static image but rather a rotating display that can be manipulated).
Thoughts on how to do that? Or alternative measures of performance? I've been using UltraVNC for the various encoding schemes so far but using TightVNC or other VNCs is also possible.
Thanks!
I'm trying to measure the relative performance of different encoding schemes across different network speeds and packet loss. One of the main ideas of measurement I have is measuring the time it takes for the following to happen:
1. Press enter on the thin client which sends data to the server and the server starts an MRI viewing application
2. Server then does all the processing work and sends the screen image data back in a preselected encoding scheme
3. The client "unpacks" the data and fully loads the image
So basically, the time it takes from the time you hit "go" to the time the image is loaded on the *client* side.
I have some ideas I'm looking into with for the "go" timestamp, ranging from just trying to timestamp on the client or timestamping when the server receives the message (and subtract off the latency and compensate for different internal times potentially), but I'm feeling stumped about how to track when the MRI image "loads" (I say "loads" because it's not a static image but rather a rotating display that can be manipulated).
Thoughts on how to do that? Or alternative measures of performance? I've been using UltraVNC for the various encoding schemes so far but using TightVNC or other VNCs is also possible.
Thanks!