You know what, the C++ Proton link you had shared seems to address some of
my questions. I think I will read up some on that before going to Python.
Thank you. Will get back if I have any questions.
On Fri, 3 Jun 2022 at 10:16, Arjee Jacob wrote:
> Yes I have seen the python tutorial examples. B
Yes I have seen the python tutorial examples. But even there I had very
basic questions like, when does the message get sent? How does the
on_sendable get initiated? What do the arguments inside the container mean
- meaning does it depend on some similar set of parameters on the receiver
side?
On
Please try raising your fd limit too. Perhaps doubling it or more.
I would also try running your proton::container with more threads, say 4
and then 16, and see if that makes a difference. It shouldn’t if your
processing within Proton is as minimal as you describe. However, if there
is lengthy
I have done some experiments raising the backlog value, and it is
possibly a bit better, I have to test it more. Even if it works I would of
course like to avoid having to rely on a patched qpid. Also, maybe some
internal queues or similar should be modified to handle this?
I have not seen transpo
On Thu, Jun 2, 2022 at 9:06 AM Fredrik Hallenberg
wrote:
> Hi, my application tends to get a lot of short lived incoming connections.
> Messages are very short sync messages that usually can be responded with
> very little processing on the server side. It works fine but I feel
> that the perform
Hi, my application tends to get a lot of short lived incoming connections.
Messages are very short sync messages that usually can be responded with
very little processing on the server side. It works fine but I feel
that the performance is a bit lacking when many connections happen at the
same time
