Posted by
| Nick Gammon
Australia (23,120 posts) Bio
Forum Administrator |
Message
| Well for timing I disabled the plugin, and then did 5 x "north" to see how long that took without the mapper:
Sent packet: 110 (7 bytes) at Tuesday, November 08, 2011, 6:51:05 AM
north.. 6e 6f 72 74 68 0d 0a
Sent packet: 111 (7 bytes) at Tuesday, November 08, 2011, 6:51:05 AM
north.. 6e 6f 72 74 68 0d 0a
Incoming packet: 234 (2 bytes) at Tuesday, November 08, 2011, 6:51:05 AM
> 3e 20
Sent packet: 112 (7 bytes) at Tuesday, November 08, 2011, 6:51:05 AM
north.. 6e 6f 72 74 68 0d 0a
Sent packet: 113 (7 bytes) at Tuesday, November 08, 2011, 6:51:06 AM
north.. 6e 6f 72 74 68 0d 0a
Incoming packet: 235 (2 bytes) at Tuesday, November 08, 2011, 6:51:06 AM
> 3e 20
Sent packet: 114 (7 bytes) at Tuesday, November 08, 2011, 6:51:06 AM
north.. 6e 6f 72 74 68 0d 0a
Incoming packet: 236 (2 bytes) at Tuesday, November 08, 2011, 6:51:06 AM
> 3e 20
Incoming packet: 237 (4 bytes) at Tuesday, November 08, 2011, 6:51:06 AM
> > 3e 20 3e 20
Incoming packet: 238 (535 bytes) at Tuesday, November 08, 2011, 6:51:08 AM
<<description>>
Incoming packet: 239 (310 bytes) at Tuesday, November 08, 2011, 6:51:11 AM
<<description>>
Incoming packet: 240 (643 bytes) at Tuesday, November 08, 2011, 6:51:14 AM
<<description>>
Incoming packet: 241 (318 bytes) at Tuesday, November 08, 2011, 6:51:17 AM
<<description>>
Incoming packet: 242 (615 bytes) at Tuesday, November 08, 2011, 6:51:20 AM
<<description>>
Using packet debug we see 5 x "north" being sent at 6:51:05. Also the MUD seems to respond with 5 x "prompt" (the > symbol) by 6:51:06, one second later.
But then the descriptions trickle down at the rate of one every 3 seconds. So it looks like the MUD is "throttling" the rate of processing commands (which would be pretty normal).
With the mapper enabled again, I seem to get similar results. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|