Give a "graphical" display over recent serverlag
- showlag <n>
Shows the amount of lag on the server by drawing horizontal bars as a function of time. Each bar represents one minute. The optional <n> argument may specify how many minutes back in time you want to view. Average CPU load for the past 15, 5 and 1 minutes is also included. Network problems (packet loss), if any, will be displayed in percent for the past 1 minute (not a graphical representation).
The values presented by this command are rough estimates only. They are obtained by counting loss of heartbeats in one specific object.
Average CPU load is not only the CPU usage for the driver, but for all processes running on the same computer as Viking.
The load average reflects how "busy" the CPU currently is. A high number may mean that the CPU has too much to do, or it can simply mean that there are many processes demanding attention at the same time. A load of 0 - 2 may not be bad at all (a bit more than 1 is common), whereas higher loads can explain why the MUD appears slow.
Network problems in the form of packet loss can explain "lag" not appearing in this graph. More than 20% is bad, and will certainly affect response time from the MUD.
If the MUD appears slow in response in despite of these numbers being low, then the problem is not local to Viking, but probably somewhere between your fingers and Viking.
If you're having problems seeing the bars, try setting 'screen term dumb'.