Hi all,
I looked through the archive but didn't see this particular issue; if
it's in there my apologies.
I'm evaluating QPID (0.6, Linux C++ broker and client currently) and
one of the requirements is to send messages that are large. "Large"
in this case could be upwards of 30MB, though in practical terms most
messages are less than 1 MB in size.
(general topology: messages sent to topic exchanges, which have 1+
durable queues bound to them.)
My tests today showed something very curious. I could send a message
up to approx. 5MB very quickly. As I passed that mark, the frame rate
slowed considerably.
565K took 0.09 seconds; 4.5MB took 0.67 seconds, 5.65MB took *31.5*
seconds. For giggles I tried a 30MB message, which I killed after
over 25 minutes of elapsed time.
When I ran with tracing turned on, I saw something very curious. The
first 78 frames (65523 bytes each) all were handled within the first
second. Each remaining frame (about 10 total) was processed with a 3
second gap between each.
I'm at a loss as to what's going on. This is repeatable, regardless of
queue size or contents. It consistently slows down at the same point.
How do I avoid this delay in these latter frames for large payloads?
Is there some kind of limiter that I'm not aware of? Is there a magic
number for message size?
Here's the client. Not particularly interesting:
Connection c;
c.open("localhost", 5672);
Session s = c.newSession();
std::string msg = "....big data.....";
std::string key = "test.12345";
Message message;
message.getDeliveryProperties().setRoutingKey(key);
message.getDeliveryProperties().setDeliveryMode(PERSISTENT);
message.setData(msg);
async(s).messageTransfer(arg::content=message,
arg::destination="amq.topic");
s.sync();
s.close();
c.close();
(the same thing happens with synchronous messageTransfer)
Thanks,
Joe
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
