Threads not showing up

[delscorcho]

Anyone know why threads wouldn't show up? In a simple test with one thread pushing timers, I only see the Remotery thread in the UI.

[dwilliamson]

Have you managed to run the sample successfully?

[delscorcho]

Yep, and the sample is working as advertised.

My actual app is relatively simple - one application thread - but that thread is extremely busy. Eventually the thread shows up in the Remotery UI, but the UI is very late to reflect any of the data. It's almost as if the Remotery thread is starved, but I can see up to date data for the Remotery thread's own profile timers. Perhaps I'll play with some of the remotery settings or instrument further to see what's happening.

[dwilliamson]

If the Remotery thread is working away then it suggests the reporting thread is doing fine. Possibilities:

• The root sample needs to be closed before any data is sent from a thread to the viewer.
• You're sending so many samples that it's overflowing the internal queues and discarding them (Remotery chooses to do this rather than block your code and affect your timing). That they show up later could mean you're sending just the right amount. Try upping the queue size and decreasing the thread sleep time.
• Some logic bug in the viewer. I have seen lots of data take a while to show up in the viewer at times and it was possibly linked to communicating the name database. There seems to be a lot of traffic communicating these names that could definitely be optimised.

Try removing some of your more frequent inner loop samples to see if it reduces the load and improves.

You might find this issue of interest: #126

[delscorcho]

Thanks for the info, Don

I did have a categorical timer wrapping a significant body of execution, so that absolutely was my problem. Should've been obvious to me that was the cause. I was getting some data in the UI that looked like hashes, and a few seconds later it filled in with readable names, so I jumped to the conclusion that I was overwhelming or starving the Remotery thread.

Thanks against for your help, and for the great profiler, and for not making it header-only, and for providing an API that considers multi-DLL applications (SetGlobalInstance), etc etc!

[dwilliamson]

Great, glad you got it sorted. Thanks for the comments!