[Xastir-dev] Xastir a CPU pig again?
Brian D Heaton
bdheaton at c4i2.com
Thu Dec 25 18:08:33 EST 2003
Tom,
Interesting. I wonder if th 100us vs. 100ms was a typo when the change
was committed?
You are also correct, I'm running Gentoo 1.4 (where I didn't ever see
the high CPU usage). I didn't see it on RH 7.3/9 either. I'm running
now on an unfiltered internet feed.
Was there ever a resolution on what was different between BSD and the
various linux distros that were experiencing the symptoms? I recall the
discussion, but don't recall is there was a final isolation of where the
interaction with the OS was causing it.
THX/BDH
On Thu, 2003-12-25 at 18:05, Tom Russo wrote:
> I can confirm it is in fact exactly the source of the problem. I
> changed the 100us delay in interface.c that had been reduced from
> 200ms sometime between 4 Dec and 8 Dec. In the 25 Dec CVS version
> this is on line 5307. Setting it to 100ms instead of 100us ended my
> problems. With that change (and no other) both the 8 Dec and current
> CVS versions of Xastir are back down to taking negligible CPU times.
>
> Now to figure out if the issue with CVS gdal instead of gdal-1.1.9 is a real
> one, or just a red herring.
More information about the Xastir-dev
mailing list