Aaron Stannard

@dependabot rebase

I increased some of EMQX's broker settings to allow up to 10,000 inflight messages at any given time and I increased the queue size to 1m messages per MQTT topic....

Great advice - thank you

@bajinder so this did not help me - pumped the receive buffer up from the default of 8kb to 1mb. Still petered out around the same point. Tried doing some...

@ingted @object I'd consider taking a look at Akka.Persistence.Sql, now that it's RTMed: https://github.com/akkadotnet/Akka.Persistence.Sql

It's faster than batchingsqljnournal anyway: https://github.com/akkadotnet/Akka.Persistence.Sql/blob/dev/docs/articles/benchmarks.md

@object that's correct - the namespaces are different for Akka.Persistence.Sql but otherwise they work identically. You can follow my upgrade tutorial to see all the steps I had to perform...

@object absolutely - the schema upgrade basically just adds support for better performing tag queries and the anti-corruption layer. You can upgrade without either of those.

> We have succesfully migrated our code to use the new Akka.Persistence.Sql. I am closing this issue. And it's working well?!

Thanks for reporting this - I think we need to tag this plugins internal messages with [`INoSerializationVerificationNeeded`](https://getakka.net/api/Akka.Actor.INoSerializationVerificationNeeded.html) so they get skipped during `serialize-all-messages=on`.