> The new code is attached: (sorry if its a bad idea to send over the list)
It's NEVER bad to send code :)
Thanks for working on this. A lot of people have been sending me mail asking
for this.
Matt
___
Discuss-gnuradio mailing list
Discuss-gnurad
I spent some more time on the waterfall display. Basically it runs
about 6x faster now. Major gains were had from precomputing the pens at
startup and from removing unecessary code in the main loop. A side
effect of these changes is that the display can have an arbitrary
mapping of value->co
On Wed, Mar 09, 2005 at 02:46:44AM -0600, David Carr wrote:
> I've spent some time profiling the waterfallsink code. Currently its
> pretty abominably slow. I'm using python's profile module to do the
> following.
>
> For a given run:
>
> total run time on cpu as reported by the command "time
Hi David,
Could you break out the creation of the Pen and Brush onto separate lines to see
what percentage of the time the object creation or the SetPen / SetBrush are
taking up. If the object creation is the problem you could pre-create an array
of pen and brushes that would be indexed by color.
Dave,
I've worked this problem a couple of times before. The fastest answer is not
to plot every point. If you instead cluster points of the same color
together, and then plot bars instead of points, the graphics algorithm will go
much faster. A piece of some code that does this looks sort
I've spent some time profiling the waterfallsink code. Currently its
pretty abominably slow. I'm using python's profile module to do the
following.
For a given run:
total run time on cpu as reported by the command "time"
real0m17.874s
user0m16.364s
sys 0m0.883s
python profile modul
