Open topic with navigation

TIBCO ActiveSpaces® - Enterprise Edition 5.0.0

# Memory Usage Considerations with the node_read_cache_size Option

The tibdg grid create command comes with the `node_read_cache_size` option. This property governs the size of the read cache allotted to a node.

Here are some memory usage considerations when you are assigning a size to the read cache:

- If the RAM on a node's host exceeds the amount of data persisted by the node, increasing the `node_read_cache_size` value to match the size of the uncompressed data set yields an improved random read performance.
- If the data set is larger than the host's RAM, increasing the `node_read_cache_size` value can negatively affect the random read performance. In such instances, the read cache of the application comes at the expense of the page cache of the operating system.

- If the value of `node_read_cache_size` is a significant percentage of the host RAM, the operating system must be configured to prevent swapping of the node application for optimal performance. Example:

  - On Linux, you might have to reduce the value of /proc/sys/vm/swappiness or disable `swap`.
  - In Docker, you can modify the `--memory-swappiness run` parameter to prevent swapping.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO ActiveSpaces® - Enterprise Edition

Copyright © 2009-2025. Cloud Software Group, Inc. All Rights Reserved.