Description
This is affecting clustered Core messages (persistent or not).
The process that cause the wrong estimation is:
- add route information to the message
- get memory estimation for paging (ie address size estimation) without accounting the new route information
- get message persist size for durable append on journal/to update queue statistics, triggering a re-encoding
- re-encoding (can) enlarge the message buffer to be the next power of 2 available capacity
The 2 fixes are:
- getting a correct memory estimation of the message (including the added route information)
- save an excessive buffer growth caused by the default Netty's ByteBuf::ensureWritable strategy
Attachments
Issue Links
- causes
-
ARTEMIS-3572 Address Memory Used increases by 60% when messages are moved to another queue
- Open
-
ARTEMIS-3577 Save Core msg re-encoding due to msg copy
- Closed
- links to