Github user mtaylor commented on the pull request:
https://github.com/apache/activemq-artemis/pull/468#issuecomment-211834401
@bgutjahr Thanks for the reply.
Yes. You are right we should get the documentation updated accordingly and
explain the pro's and cons of each approach, fixed, unbounded.
With regards to heap size, I am trying to figure out how each thread
manages to increase the heap by 500MB. this seems huge, if this is the case we
need to figure out what is causing this. Perhaps sending lots of large
messages concurrently could cause this? Though if this is the case unbounded
pool probably wouldn't help... Might you mean stack space by any chance? If
so this does seem like a very high number and I'd recommend exploring why this
is set so high.
Yes I see the issue with timeout. What you described was my original
concern the first time round which is why I left it out. If you decrease the
timeout further you'll likely get a performance hit, as you'll be constantly
creating new threads (which with large stack size would be even more costly).
I think what we are missing with regards to defaults, is some performance
numbers, really these are just guesses, looking mostly at what Netty does. I'm
interested in your use case. Particularly understanding why the heap grows so
large, because I think this is something that needs addressing. Do you have
any more info on this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
