Streamline : Lag in capture

I see. So it gets slower / increasingly laggy over time.

Typically, lag like that happens when the connection to the target is saturated, or where the target is configured to produce a significant amount of data (usually, SPE is enabled).

To check, you haven't recently made any changes (updated version of Streamline, changed board or different configuration on target) ?

It looks like you are connected to a remote target over TCP/IP...

* What is the target you are running on? (OS, hardware type, number and type of cpu cores)
* Have you tried restarting the target device?
* What sort of counter configuration have you requested?
* Since you are running gatord on the remote target, what command line options did you pass to launch?

Can you launch gatord with the debug flag and capture its output during a short capture, then send it here. To do so:

gatord -d ...your other arguments... 1> gatord.log 2>&1

I see. So it gets slower / increasingly laggy over time.

Typically, lag like that happens when the connection to the target is saturated, or where the target is configured to produce a significant amount of data (usually, SPE is enabled).

To check, you haven't recently made any changes (updated version of Streamline, changed board or different configuration on target) ?

It looks like you are connected to a remote target over TCP/IP...

* What is the target you are running on? (OS, hardware type, number and type of cpu cores)
* Have you tried restarting the target device?
* What sort of counter configuration have you requested?
* Since you are running gatord on the remote target, what command line options did you pass to launch?

Can you launch gatord with the debug flag and capture its output during a short capture, then send it here. To do so:

gatord -d ...your other arguments... 1> gatord.log 2>&1

Actually, i missed your first reply, so missing some of the information that answers some of above, but if you could still answer:

* What sort of counter configuration have you requested?
* Since you are running gatord on the remote target, what command line options did you pass to launch?
* Can you launch gatord with the debug flag and capture its output during a short capture, then send it here.

Additionally, if you are happy, can you "Export" one of the capture files that show this lag and send it to us, so I can examine it.

Thanks

Thanks.

If I run your capture through our replayer, it renders correctly (no lag), so I don't think there is some bug being triggered in the U/I that is causing the slow down. Looking at the log, as you say, looks like a pretty typical device with small number of cores / counters, so not particularly anything that would cause some processing bottleneck.

I wonder, if you run gator in headless mode, if it captures as expected, or if you still see some lag. You can make a local capture (to disk on the target) with something like:

time sudo ./gatord -c configuration.xml -o capture.apc -t 25

I have reinstalled gator and ARM Streamline it still shows the message "Session already in progress
Failed to set up Annotations UDS parent listener. Is the socket already in use?
" but capture is working fine now.

I think some files might got corrupted/changed due to the reboot. Thank you for the help and support 

No worries. Glad it was fixed!

That message can be ignored, it is just informative, we should really suppress or change the wording of it...