Don Williamson
Don Williamson
@conversy Can you verify your tests on latest for this?
We have the start of a `Settings` object here: https://github.com/Celtoys/Remotery/blob/a910605b92c5d9a1306352f9ffcaad716b2a4fb7/vis/Code/Remotery.js#L9-L17 This should be stored in `LocalStore` but right now it's not. All we store there is the last connection address...
Sorting has gone in here https://github.com/Celtoys/Remotery/commit/6cea510dad1db3a50cf81d3147db3c10e3c24608
Could force message sizes to be multiples of something like 512. Then unlocking would require setting every 512th byte to zero instead of a memset. Obviously the smaller the size...
Yes, all this is known but it's very tricky to make all this cross-platform and integrated with Remotery's unique command queue that is MpSc while allocating all its variable-size message...
Have you tried increasing the size of the message queue?
Actually, it's worth mentioning that Minitrace uses a mutex for pushing events which in cases of high contention won't give you accurate traces. There's every chance that threads queued for...
It should handle contention fine. I think what's happening is a combination of two things because you're sending data so fast: * The message queue to the main thread is...
Bear in mind the only way to not lose data unconditionally is to block the thread issuing the sample and I don't want Remotery to do that, ever. So it'll...
It still reduces to the same problem: if you are writing to the queue faster than data is being pulled from it, you will have to block. The only solution...