#57 Ping time defaults to 0.1ms

[Anonymous]

Originally created by: Killeroo

[[VERY GOOD Article that should be used as reference on the matter]](http://aakinshin.net/blog/post/stopwatch/)

General behavior:

• Starts when error or other packet type is received
• Normally occurs when when data is recieved from other address than that being actively pinged (eg hub addresses like 192.168.1.255 etc)
• Also occurs when another PowerPing instance starts pinging same target
• Does not occur due to timeout

Could be caused by responseTime.Restart(), MSDN page states 'resets the elapsed time to zero, and starts measuring elapsed time.' could be prematurely starting stopwatch..

Possible solutions

• Could be due to StopWatch object not resetting properly in final clause (Ping.cs: line 404), could use StartNew (maybe not...) (msdn.microsoft.com) or Reset (maybe not either..) (msdn.microsoft.com) instead of restart.
• Alternatively could use Timer class for some more low level control, utilizing its .interval (msdn.microsoft.com) method. HOWEVER there could be concerns here about accuracy
• Could be how we are using timespan in display.cs? (stackoverflow.com) (Spoilers I think Display uses DateTime not timespan)
• Could possibly use raw StopWatch data to get more accurate readings, rather than using methods as shown here and also here

Todo

• [x] Add feature to specifiy level of detail with time (decimal 1.23 or just 1 ms)
• [x] Implement more accurate and safe time management or look into way of isolating PowerPings properties or resources being used in other instances. Good article on good .NET practices, mentions app domains and how the code is structured on a low level (msdn.microsoft.com) and Another good one relating more to performance

[Anonymous]

Originally posted by: Killeroo

Also seems to happen after an error packet is received:

[Anonymous]

Originally posted by: Killeroo

when pinging same address from another PowerPing instance time. Only occurs if pinging same address, time never recovers to normal readings only bounces between 0.1 & 0.2ms: