How to tune Dapr bulk publish/subscribe for maximum throughput

1. enterprise-wasm

   1 1 15 8.5 HCL

   Evaluate various WebAssembly back-end frameworks and tool-chains for enterprise workloads

   

   While exploring other hosting and compute options like Dapr, WebAssembly and Spin I realized, that this kind of implementation causes a lot of traffic in the Dapr to application communication which can easily stand in the way of faster compute processing.

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. message-distribution

   2 2 1 7.6 Bicep

   

   all code snippets shown hereinafter, can be followed along and found in dapr-pubsub branch of the repository I already used in the previous post

4. components-contrib

   3 3 555 8.9 Go

   Community driven, reusable components for distributed apps

   

   Changing this setting did not make the warning completely go away. As Alessandro Segala states in this issue : "This happens because when it's time to renew the locks, at the interval, we "snapshot" the active messages and then renew each one's lock in sequence. If you have a high number for maxActiveMessages, it takes time for the component to renew the locks for each one, and if the app has ACK'd the message in the meanwhile, then the lock renewal fails."

Suggest a related project