Re: Change minLargeMessageSize on Artemis
Just as a personal note: in order to make an efficent use of the default
garbage collector G1, it would be a good practice to verify with your
expected typical load if
there are happening humongous allocations (
If they will happen I suggest to tune -XX:G1HeapRegionSize to be >= twice
the chosen minLargeMessageSize (or better, the expected maximum encoded
message size, if known).
That's to avoid having poor performances due to a misconfigured GC.
Anyway in the article is well written everything I have just explained
Il giorno ven 4 mag 2018 alle ore 14:06 nigro_franz <nigro.fra@xxxxxxxxx>
> I can't tell what else should be needed on clustered env but:
> - on the (core) client you have to add minLargeMessageSize on your URL
> parameters eg tcp://localhost:61616?minLargeMessageSize=<put here the value
> you need>
> - on the server you have to change/add journal-buffer-size on broker.xml in
> order to be >= minLargeMessageSize
> Probably i'm just paranoid but I will change the consumerWindowSize on the
> client to be >= minLargeMessageSize as well, but I could be wrong on that.
> Sent from: