how-to block ads
|
|
Share Topic
 |
 |
|
|
|
 ScreeIn the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ
 ·Comcast
2 edits | reply to peter_m
Re: [Util] "D-Link Connection Monitor" utility said by peter_m:but why does it change over time, even with the "do not adjust time" option selected? If it's not adjusting, is the router drifting? You can see from the router's own log that its own boot time calculation drifts. For example, when you first boot the router, in the Status page log note the date and time of the first entry. If your log doesn't fill up too fast and remove entries, after a while you will see the date and time of the first entry is different. My guess for this drift is that the router's own up time is not quite on par with real time, that is as real time and the up time both progress forward, the router is either not progressing its up time accurately (or it just keeps lousey real time, dunno for sure -lol). Can visualize it this way:
At boot time, we start even as stay close for a while:
Router Up Time: 0, 1, 2, 3...etc
Real Time: 0, 1, 2, 3...etc
Now as we go longer, real time is of course real, so it's assumed constant and correct. Howerver, the router must be counting it's up time too fast, like:
Router Up Time: ...360, 361.0001, 362.0012, 363.0037...etc
Real Time: ...360, 361, 362, 363...etc
So the up time is drifting forward ahead of real time too much, and when I calculate the boot time by subtracting the up time from now (the real time), it will keep subtracting too much over time and therefore keep changing. To combat this, I determined the percentage of drift of my router over a day, and subtract that much extra of the current up time from now, and it works well for my router. But because different routers probably drift differently, I am adding a configurable percentage setting so one can determine their own to use for an accurate result.
[Please note I may have it reversed, that is the router may not be adding to its up time enough over time, rather than adding too much up time. But you get the idea.:)] | |
 peter_mPremium
join:2005-07-13
Canada, QC | Thanx for the explanation scree.:D | |
zooos
join:2005-09-11
Dearborn, MI | reply to Scree
First of all Thanx a million for the great utility.
Lately with all the upgrades, i guess it's getting larger and it freezes every now and then, eating up alot of CPU.
This is a screenshot with 2384 concurrent connections, could this be a problem and the cause of the freezing??? | |
ScreeIn the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ Reviews:
·Comcast
4 edits | Well, wow, with 2384 lines to process, I suppose that would be the cause. I have found it's the text coloring routine that causes the high cpu when there are many entries. I will try to find a better way to be more cpu-friendly. 
Also note that there may be a freeze when trying to determine network computer names, due to the api timeout that is not changeable (about 15-20 seconds) that occurs when a computer is no longer available but its IP is still in a router entry. I use a cache to avoid this but it clears every 5 minutes, so such a freeze may occur every 5 minutes for 2 or 3 times until the router drops the entry (or that computer comes back on the network). | |
ScreeIn the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ Reviews:
·Comcast
| reply to Scree
Download change... Sorry was unavailable for a while:
»home.comcast.net/~scree/public/D···itor.zip
| |
|
