#1 Test comms latency

closed
nobody
core (7)
8
2005-11-15
2004-06-15
Alex Brooks
No

Using a simple (example) server and client, send a heap of objects and measure the average latency.

This would be easiest for synchronous calls (query), but there's surely a way to do it for asynch too.

Variables to vary:

- comms pattern
- connection type (intra-host, inter-host, wired, wireless)
- object size (type?)

Should make a note of processor load while doing htis too.

Discussion

  • Alex Brooks

    Alex Brooks - 2004-06-16

    Logged In: YES
    user_id=720003

    Should also provide a standard against which to evaluate whether a given latenxy is 'fast' or 'slow', eg:

    - round-trip latency of ping (trivial to implement)
    - crudg (harder to implement)
    - simple socket (harder to implement again)
    - Player (hard to implement, given Player's fixed update rate)

    Definately don't need to test all of these, perhaps ping is enough.

     
  • Alex Brooks

    Alex Brooks - 2004-06-28
    • priority: 5 --> 8
     
  • Alex Brooks

    Alex Brooks - 2005-11-15
    • status: open --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks