For testing scripts, I'm not really sure how to track down problem ones. It would be easier if it were my own code, as I'd know which bits are easily disabled, and even which ones are called the most or are the least well written.
There is a display in mudlet (bottom right) which shows last latency, and last script execution time.
I don't suppose that is a variable I can access, is it? If it is, I could perhaps write a script that logs script execution times or something to that effect.
measuring parser speed
Re: measuring parser speed
getNetworkLatency() will return that value.
Re: measuring parser speed
Latency is the ping to the server that I am connected to.fetaera wrote:getNetworkLatency() will return that value.
Two figures are displayed down there, one is network latency, the other is script execution time.
I could go about using the stopwatch functions to create a debugging log, but I feel that the timing is already being done, if can just hook into it.