Oracle Connector Driver Nodes | QueryGrid - Oracle Connector Driver Node Guidelines - Teradata QueryGrid

QueryGrid™ Installation and User Guide - 3.06
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata QueryGrid
Release Number
3.06
Published
December 2024
ft:locale
en-US
ft:lastEdition
2024-12-07
dita:mapPath
ndp1726122159943.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
lifecycle
latest
Product Category
Analytical Ecosystem
Important:
  • The Oracle connector is a target connector only and cannot be used as an initiating connector.
  • All Oracle target connector nodes must be driver nodes for communication and data transfer to the Oracle system.
  • Install the Oracle target connector on an edge or additional node and not on Oracle system nodes.
The following are the minimum requirements for an Oracle target connector node to install the QueryGrid 3.x software:
  • 16GB RAM
  • 50GB disk space
  • Memory requirements as defined in the fabric/connector setup
  • CPU and JVM configuration for large dataset processing
  • Latest version of JAVA 8 or 11
  • For supported operating system versions, see the QueryGrid Compatibility Matrix

When using the Oracle Connector, the system running the QueryGrid driver process handles a greater workload as compared to other connectors. The CPU and memory configuration of the driver node has a significant impact on query performance. The following sample test results are from using different CPU and memory configurations. Multiple driver nodes can be used for load balancing.

CPU

The driver node can reside on a physical system or a virtual machine. The following query utilization results are from both system types:
Machine Type Import Export
Physical System (56 CPUs, 252GB memory) 3% 2.5%
Virtual Machine (2 CPUs, 16GB memory) 70% 55%
Garbage collection time is greater on the virtual machine than on a physical system:
Machine Type Import Export
Physical System (56 CPUs, 252 GB memory) 500ms 300ms
Virtual Machine (2 CPUs, 16 GB memory) 600ms 450ms
CPU utilization increases as the number of concurrent queries increase (maximum of 5 concurrent queries):
Machine Type Import Export
Physical System (56 CPUs, 252 GB memory) 45% 1%
Virtual Machine (2 CPUs, 16 GB memory) 90% 55%

Memory

The default JVM driver has a default maximum heap size of 500MB. Teradata recommends increasing this value to 10GB when using the Oracle connector due to the increased workload experienced by the driver node. You change the value by setting the QueryGrid system property driverMaxHeapSizeMB to 10000 (10GB) and restarting the tdqg-node service. Heap usage increases with the number of concurrent queries.

Throughput

Throughput per query decreases as more concurrent queries are run, but the total throughput of the system increases.
BYNET connection is used between Teradata and the driver node for the reference data in the following table:
Machine Type Import Throughput

(Single Query)

 Export Throughput

(Single Query)

 Import Throughput

(5 Concurrent Queries)

 Export Throughput

(5 Concurrent Queries)
Physical System

(56 CPUs, 252 GB memory)

 11.11MB/s 7.03MB/s 3.97MB/s per query 1.40MB/s per query
Virtual Machine

(2 CPUs, 16 GB memory)

 11.71MB/s 7.23MB/s 3.31MB/s per query 1.71MB/s per query