[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Serious performance regression in Gnu Radio recen
From: |
Marcus D. Leech |
Subject: |
Re: [Discuss-gnuradio] Serious performance regression in Gnu Radio recent |
Date: |
Sun, 05 Feb 2012 16:44:08 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 02/05/2012 04:08 PM, Tom Rondeau wrote:
So, what if it was your *own* commit that seemed to be causing a
problem? Wouldn't that be embarrassing? I think so :-( :-(
commit 2a2411a598c222e2ef82b857c0b53e0a9d1daf3f
Author: Marcus Leech <address@hidden>
Date: Sun Jan 15 23:49:52 2012 -0500
core: fix for off-by-one issue in strip chart. Increases buffer
size for longer displays.
I have no idea why this should be a problem, the buffer-shifting for
stripchart mode is all done on the C++ side, and the updates are
done at a fairly lazy rate (a few Hz). So it's probably an issue on
the Python side with bigger plot buffers. Perhaps there's some kind of
N**2 scaling ugliness going on that wasn't immediately obvious to me
when I did that patch.
I think ultimately, the plotting stuff has to move so that most of the
computational stuff is done in C++ land, with only the thinnest pieces
done on the Python side.
--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org