[MUD-Dev] Benchmarking MUDs

[Adam Martin]

From: "Ian Collyer" <i.collyer at ntlworld.com>

> Prime targets for benchmarking MUDs must be...

>   - Memory
>   - Processor
>   - Bandwidth
>   - Disk space

That only covers the results from the server view of life. Client
view of a MUD would be interested in extra things:

  - Latency (marginal, as opposed to infrastructure-imposed e.g. the
  inherent latency of my modem dial-up)

    - + various different areas for latency

       - command-confirmation (did that click / typed command do
       anything? )

       - push-data (oh look, someone just walked in front of me, can
       I aim at them before they disappear)

       - social interaction latency (above a critical threshold -
       surely researched especially in context of military and
       trans-atlantic phone calls - communication latency seriously
       wrecks the abilitiy to hold a conversation)

  - Client bandwidth used (as opposed to total bandwidth)

  - Client processing (for all MUDs that use or need specialized
  clients)

  - + probably others but these were off the top of my head

Adam M
_______________________________________________
MUD-Dev mailing list
MUD-Dev at kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev