On 02/27/2014 02:56 PM, Tor Rune Skoglund wrote:
A good. Thanks a lot! :)
(Still, technically, it should probably be possible to add that feature
on durable messages also - i.e. sharing the same payload reference?
Yes. We're always happy to accept code contributions :)
And, btw, I presume durable in this case is referring to the message
(i.e. "persistent"), and not durable queue/exchanges? We are in the
process of learning Qpid here, so the terminology can be a bit confusing
at times... :) )
For a message to consume space on disk, both the message and the queue
it's on must be marked as durable. We allow interleaved durable and
transient messages on the same durable queue.
Best regards,
Tor Rune Skoglund, [email protected]
Den 27. feb. 2014 20:36, skrev Ted Ross:
Speaking for the C++ broker:
If the messages are transient (i.e. not durable), the enqueued
messages will all be a reference to a single in-memory instance of the
message content. Don't use durability for these cases, they will be
individually stored on disk (requiring 4TB of journal space).
-Ted
On 02/27/2014 02:23 PM, Tor Rune Skoglund wrote:
Hi,
when sending large messages (say, 4GB) from a server to a group of
receivers (say, 1000 of them) where each of them have their own queue on
the server side, will the server side broker queues "refer" to the same
payload (in memory/on disk), or will the payload get duplicated on each
queue?
Best regards,
Tor Rune Skoglund, [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
