Tibco Data Virtualization (TDV) Configuration Possibly Prevents Out of Memory (OOM) Errors
Article ID: KB0081947
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | 7.0.6 |
Description
Introduction
This document describes the best practices used in order to prevent a Tibco Data Virtualization (TDV) crash with an Out of Memory (OOM) error.
This document describes the best practices used in order to prevent a Tibco Data Virtualization (TDV) crash with an Out of Memory (OOM) error.
Issue/Introduction
Introduction
This document describes the best practices used in order to prevent a Tibco Data Virtualization (TDV) crash with an Out of Memory (OOM) error.
Resolution
Tibco Data Virtualization (TDV) Configurations that Prevents OOM Errors
Increase Total Memory
Increase the total memory. Choose Administration > Configuration > Composite Server > Memory > Java Heap > Total Available Memory (On Server Restart) in the Studio and select the maximum value available on your machine that can be allocated to the Tibco Data Virtualization (TDV) service.
OOM errors usually result from a single request that consumes the entire available Java Virtual Machine (JVM) heap. You can prevent this when you set a limit on the amount of memory that requests are permitted in order to take from the JVM heap.
Increase Total Memory
Increase the total memory. Choose Administration > Configuration > Composite Server > Memory > Java Heap > Total Available Memory (On Server Restart) in the Studio and select the maximum value available on your machine that can be allocated to the Tibco Data Virtualization (TDV) service.
Note: If you change this setting, you must restart the sever.
Reduce Memory-Per-RequestOOM errors usually result from a single request that consumes the entire available Java Virtual Machine (JVM) heap. You can prevent this when you set a limit on the amount of memory that requests are permitted in order to take from the JVM heap.
- Set the limit and choose Administration > Configuration > Server > Memory > Managed Maximum Memory per Request properly in Studio.
- Change the default value of 100 to 70% or less based on your test results.
Caution: Do not limit managed memory too severely. A low setting might slow valid requests for disk paging and queue processing.
Note: Memory-intensive queries might have a slower response time because they can no longer consume the entire available heap.
Note: Memory-intensive queries might have a slower response time because they can no longer consume the entire available heap.
Feedback
Yes
No
Powered by
