Github user iskl commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/29
Dear @shroman , thanks for your suggestion :)
In my concept, broker thread is **time sensitive**. When broker thread in a
MQ broker is in I/O operation and GC occurs, an **I/O competition** appears
between broker thread and GC thread. It may bring **long time latency to broker
thread**.
Linux distributions based on the 2.6 kernel and later offer `/dev/shm` as
shared memory in the form of a **RAM disk**
[(link)](https://en.wikipedia.org/wiki/Shared_memory). Pointing GC log to
`/dev/shm` can avoid I/O competition between broker thread and GC thread.
In conclusion, I tend to use `-Xloggc:/dev/shm/mq_gc_%p.log` :)
---
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.
---
