AntonRoskvist opened a new pull request, #4413:
URL: https://github.com/apache/activemq-artemis/pull/4413
…alse
I'm very open to the idea that this might not be the right solution but if
nothing else the test works to demonstrate the issue.
Can also very easily be demonstrated by:
configuring <journal-sync-transactional>false</journal-sync-transactional>
<journal-sync-non-transactional>false</journal-sync-non-transactional>
Starting the broker
Sending some messages i.e:
bin/artemis producer --destination queue://TEST.1 --message-count 100
Wait _any_ amount of time
kill -9 artemisPID
Start broker
Messages are gone
This is new behavior since broker version 2.18.0
I have run some local performance tests between this change and an unchanged
broker and can see no meaningful difference in terms of resource utilization or
overall throughput.
I have tested with sync=true and false,
paging 50% of the messages
Running all message production in transacted batches of 10 messages each
Running all message production with AUTO_ACK
Results of the tests:
```
1M messages
max-messages=500k
sync=false
batch
PR: 231995 ms
ORG: 234791 ms
AUTO_ACK
PR: 33627 ms
ORG: 31928 ms
sync=true
batch
PR: 254064 ms
ORG: 247203 ms
AUTO_ACK
PR: 2438805 ms
ORG: 2439546 ms
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
