fermyon
Improved rumqttc event loop check.
The CI failure in the plugins test is because an external web server is returning a different error from the one we expected; it has nothing to do with this PR and can be overridden (assuming there are no other failures)
@suneetnangia Is this intentionally still draft? No rush, just checking that it's deliberate.
@suneetnangia Is this intentionally still draft? No rush, just checking that it's deliberate. We can merge now, I was trying to see if there's any better way, will raise subsequent PR as needed but for now it brings stability to the publish part.
@itowlson do we have a performance testing project for these outbound and triggers components? Ideally, I want to hammer MQTT trigger and publish component at some point. For now, I have improved the code but I definitely think it can be better e.g. running eventloop async task as soon as connection is created, I'll spend sometime on it later. Thanks
~@vdice Can you force merge this please? The CI error is unrelated to the PR.~
Since our last comment here, I've tested a better solution (as I alluded to) with a few thousand messages (100k or so). Updated.
@suneetnangia Not to rush you, but do we have a way forward here? Failing that, is there an intermediate solution that's "better than today" even if not perfect? Thanks!
@suneetnangia Not to rush you, but do we have a way forward here? Failing that, is there an intermediate solution that's "better than today" even if not perfect? Thanks!
@itowlson this PR now have the fix (rolled back latest one) which makes it much better than it's current state (in fact current does not work), if we can get this in for now and I'll look at better solution next week... have some time off.