I have a ‘fun’ problem I’m trying to sort out. Bear with me!
I’ve been running a Raspberry Pi 1 B+ for a year or so as an NTPsec Stratum one timeserver - using the GPS Hat (Here’s how you can make your own: https://www.ntpsec.org/white-papers/stratum-1-microserver-howto/)
It runs very nicely and reliably. Several days ago, I set up NTPvis on the Pi, in order to graph the performance. It generates lovely details of how the Pi is doing as a timeserver. I also started collecting temperature data, and that’s where things go a bit sideways. From the graphs, it’s become clear that the daily temperature variations are a big factor in overall accuracy of the clock. That I’m going to address separately (different case maybe, or other sort of insulation to even things out)
What also became immediately apparent however is that generating these graphs that showed me that issue, also fairly dramatically affects the temperature also!
You can have a look at the graphs here: https://ntpsec.anastrophe.com/
If you look at the temperature/frequency graphs, you’ll see the very regular big spikes in temp - those are what happen each time NTPvis runs to generate the graphs. (The glitches mid-graph are from some testing I was doing, they normally aren’t there)
Because of those spikes, it occurred to me that I have two option - get a Raspi 3 B+, put the GPS HAT in it and hope that a more powerful, quad-core box will be able to chew through those logs with much more ease than the puny Raspi 1 B+. That may then keep the temp more even.
OR, I get the Raspi 3 B+, and run it as a separate data-crunching machine - rsync the ntp log data over to it from the existing Raspi 1 B+, where it will chew through it without any temperature impact at all on the actual clock box. Or maybe NFS, still contemplating.
(You might have guessed that this was just a great excuse to buy another new Raspberry Pi to play around with, and it is!)
I guess a third option is to run the Raspi 3 B+ as the clock, and use the Raspi 1 B+ as the data cruncher - it’d be a lot slower, but there’s no real hurry to generating the graphs. I wonder if the more efficient hardware of the 3 B+ might have an even smoother temperature curve overall.
Certainly, I can test each one of these scenarios, although doing so would incur a lot more downtime, which I’d prefer to avoid.