此内容没有您所选择的语言版本。

Chapter 43. Performance Tuning


In this chapter we will discuss how to tune HornetQ for optimum performance.

43.1. Tuning Persistence

  • Put the message journal on its own physical volume. For example, if the disk is shared with a transaction coordinator, database, or other journals which are also reading and writing from the disk, these may greatly reduce performance because the disk head may be skipping between the different files. One advantage of an append only journal is that disk head movement is minimized - this advantage is destroyed if the disk is shared. If using paging or large messages, ideally, ensure that they are put on separate volumes.
  • Minimum number of journal files. Set journal-min-files to a number of files that would fit the average sustainable rate. For example, if new files are being created on the journal data directory too often and lots of data is being persisted, increase the minimum number of files, this way the journal would reuse more files instead of creating new data files.
  • Journal file size. The journal file size should be aligned to the capacity of a cylinder on the disk. The default value 10MiB should be enough on most systems.
  • Use AIO journal. If using Linux, try to keep the journal type as AIO. AIO will scale better than Java NIO.
  • Tune journal-buffer-timeout. The timeout can be increased to increase throughput at the expense of latency.
  • If running AIO, it may be possible to increase performance by increasing journal-max-io. DO NOT change this parameter if running NIO.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat