<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 6/12/19 17:00, Gary E. Miller wrote:<br>
<blockquote type="cite"
cite="mid:20190612170019.486acea4@rellim.com">
<pre class="moz-quote-pre" wrap="">Yo Paul!
On Wed, 12 Jun 2019 16:53:42 -0700
Paul Theodoropoulos <a class="moz-txt-link-rfc2396E" href="mailto:paul@anastrophe.com"><paul@anastrophe.com></a> wrote:
frequency offset similar, etc. Do the GPS logs factor into the other
statistics generated, in some way? I can't imagine they would -
jitter is jitter, the whole world 'round...right?
</pre>
<pre class="moz-quote-pre" wrap="">
Weird. Maybe ntploggps is keeping your CPU from doing a microsleep
or cutting the clock speed? Maybe it keeps gpsd from getting swapped
out or?
RGDS
GARY
</pre>
</blockquote>
<br>
Maybe on the microsleeps, yeah. I've noticed that ntploggps uses a
"lot" of cpu time relative to ntplogtemp for example, so it does
introduce a continuous load. I have my cpu pegged at 'performance',
and using cpu partitioning to keep ntpd on core 2 and gpsd on core
2, so it shouldn't be moving around. But hey, it's an RPI, I've
squeezed the living daylights out of performance tweaking it. I
think the microsleeps is probably the "culprit", which I'm happy to
have, now to start monitoring ntploggps so it'll get restarted if it
dies again!<br>
<br>
<pre class="moz-signature" cols="72">--
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a></pre>
</body>
</html>