CPU load when monitoring many stations about seedlink_plotter HOT 3 OPEN

I suspect that this is due to the fact that trace list is regenerated every time the the merge method is invoked

Yeah, we started this as simple as possible to start out with just relying on everything that's already there, development time vs. CPU's doing some more stupid number crunching .. ;-)

This reduces the CPU load on my machine from 100% to 10-20%

Sounds great! 👍

I noted that the CPU usage quickly increased to 100% on my machine.

I'd be curious whether this impacts the minimum realizable update time, i.e. whether you can go to a smaller plot update time with that? The plot is in a different thread, so probably not, I guess? But the stream to plot might be more up to date, I guess..

Actually, there's a lot more in there that's probably not needed, all the super-tedious checking of sub-sample alignment.. hardly necessary for just a simple kiosk plot. ;-) ..but again, as long as it works..

In any case, I think it would be great to have your modification in master. Care to do a PR?

from seedlink_plotter.

I'd be curious whether this impacts the minimum realizable update time

I cant really tell, since in reality I only use the data retrieval part from the seedlink_plotter for a different application that I'm working on. At a latter stage I'll probably want to include some plotting as well and will then probably have a peak at the plotting part to get started. That said I actually also have several threads running that are accessing the collected streams but as these always makes a deep copy of the stream object and then operates copy (as is done by the seedlink_plotter). As the copying part seems to be quite efficient, this does not seem to be problematic (neglecting here the load from the work performed by the thread which is a different issue)

Care to do a PR

I would be very happy to contribute to this very nice and useful project : ). However, I think there's still some work to be done before my suggested solution is decent/general enough, and I also have to read up on how to do a PR (presumably not that hard but...).

from seedlink_plotter.

some work to be done before my suggested solution is decent/general enough,

Great, just let us know when you have something!

and I also have to read up on how to do a PR (presumably not that hard but...).

Let us know if you're struggling and need directions with that..

from seedlink_plotter.