Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Memory and Heap Size Guideline for Cache Agents

Guidelines for memory and heap size depend on the cache provider.

## With Legacy ActiveSpaces as The Cache Provider

The JVM can use much more memory than expected because it often defers garbage collection. If the JVM uses a large percentage of the available physical memory, the Legacy ActiveSpaces cluster might not perform well, due to swapping. The JVM and Legacy ActiveSpaces run in the same process; therefore they compete for the same addressable space in the RAM. If the JVM uses a large percentage of the addressable space, out of memory errors can occur in the Legacy ActiveSpaces cluster. This situation is more likely to occur on 32-bit systems, where the addressable space is 4GB or less. To avoid this situation, set a heap limit to restrict the amount of memory used by the JVM, so that it does not compete with Legacy ActiveSpaces. For example, you could use the command line option `-Xmx512m`.

Did you find this helpful?

YesNo
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 BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.