You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think as stated in the example it uses goroutines, so no problems with that and no performance benefit over calling over threads, the session is managed by the library unless you create multiple connections, some problems you gonna get is a timeout and the disconnections over a large number of submitSM, you should use rate limit and config the window param accordingly.
RateLimiter: rate.NewLimiter(rate.Limit(maxFreqLimiter), 1), // x per second is a good way to control it.
@alexanderomnix thanks for replying. I observed that tx.Submit takes 250ms to complete. Which means on a single connect max TPS of 4. And that is the reason, I asked if I can use go routines. Correct me if am wrong here
Can I use tx.Submit in thread ? I can see in the example_test it is used inside http Handler function
Also if I use tx.Submit in 10 threads, the delivery receipts traffic would increase. Will the Handler function of Transceiver perform fast enough ?
The text was updated successfully, but these errors were encountered: