I've been monitoring this thread for a while and i have a few comments.
1) I think on average the TX queue delay inside an ethernet card is going to be
way smaller than the delay observed on the general internet. NTPd's primary
algorithms compensate really well for jitter and delay already so the
> I thought of that too but rejected it as way too machine-specific. Because
> the clock PLL does not track frequency ramps feed-forward could be very
> effective (e.g. order of magnitude). To make this work however, you need to
> first discover which one of many potential temperature sensors
Thank you to all who replied to my inquiry!
Regarding required accuracy...there really is none in my case. It's just
a matter of "how good can this get?" However, the results may be of
actual use to others, just not me.
I have gone to the effort of implementing the interleaved symmetric mode
Holy cow!
I thought of that too but rejected it as way too machine-specific.
Because the clock PLL does not track frequency ramps feed-forward could
be very effective (e.g. order of magnitude). To make this work however,
you need to first discover which one of many potential temperature
senso
If you have Windows/Linux on Intel/AMD mobos, try OpenHardwareMonitor on
Windows with .NET 2+ and Linux with Mono and Winforms:
http://openhardwaremonitor.org/documentation/ and
https://github.com/openhardwaremonitor/openhardwaremonitor.git
--
Take care. Thanks, Brian Inglis, Calgary, Alberta,
Here are two other ideas you might want to consider to improve accuracy:
Feed forward (PID) control on system temperature and significant changes in
system load. Let me describe the situation. Right now I have only 3
computers on a home LAN. Two, one of which is my main system for email and
dict
