Memory Settings
CData Virtuality Server を実行するには、かなりの量のメモリが必要です。CData Virtuality Server が多くのオペレーションを実行したり、膨大な量のデータを処理する必要がある場合は特に、高速で安定したサーバーのインストールにはメモリの提供と構成が重要です。
CData Virtuality Server のメモリは、JVM ベースのメモリ設定と BufferManager 設定によって構成されます。
CData Virtuality Server には、ローカルリソースに応じてメモリ使用量を設定する自動調整メカニズムがあります。
Auto-Adjusting
CData Virtuality Server 起動スクリプトは、起動時に「メモリ設定の推奨」で示されるメモリ設定を自動的に行います。
%pathToDVserver%/bin/standalone.conf (Linux)/ %pathToDVserver%/bin/standalone.conf.bat (Windows) ファイルのanalytic_storage_on_different_host_dv
パラメータを使用してスクリプトを構成できます:
Parameter | Value |
---|---|
|
|
Configuration Files
メモリーの設定は以下のファイルにあります:
Operating System | File | Comment |
---|---|---|
Linux | %pathToDVserver%/bin/standalone.conf | Contains JVM-based memory settings |
Windows | %pathToDVserver%\bin\standalone.conf.bat | Contains JVM-based memory settings |
Linux/Windows | %pathToDVserver%/standalone/configuration/dvserver-standalone.xml | Contains memory settings of the application server |
On Windows platforms, it is possible to configure JVM memory settings in different files.
We do not recommend doing this! If memory settings are found in different locations, the server will use the ones read last.
If you find duplicate startup options in the boot.log file, remove memory settings from all locations other then standalone.conf.bat
. They may reside in the following places:
%pathToDVserver%\bin\standalone.bat
%pathToDVserver%\bin\service.bat
JVM Settings
JVM 設定でCData Virtuality Server プロセスのMemory 設定を構成できます。ヒープ・メモリの量と割り当てられた総メモリを適切に構成することが重要です。
JVM option | Example | Comment | |
---|---|---|---|
|
| Minimum amount of heap memory | |
|
| Maximum amount of heap memory | |
|
| Maximum total size for new Java I/O package direct buffer allocations |
|
|
| Size of cache used to store code which Java's compiler will access |
BufferManager Settings
BufferManager はCData Virtuality Server によるメモリとディスク使用量の追跡を担当します。BufferManagerを適切に構成することは、高いパフォーマンスを確保するために最も重要な部分の1つです。
BufferManager の設定はCData Virtuality Server フォルダのbuffer-service
セクション、%pathToDVserver%\standalone\configuration\dvserver-standalone.xml ファイルに保存されます。以下はその例です:
<
buffer
-service
memory-buffer-off-heap
=
"true"
max-storage-object-size
=
"134217728"
/>
Application Server Setting | Default Value | Description | Remarks |
---|---|---|---|
|
| Total size of batches that the BufferManager can hold in memory. The default value | Specified in KB without a measurement unit |
|
| Total size of batches that can be used by active plans regardless of the memory held based on The default value of | Specified in KB without a measurement unit |
| 2048 (in MB) | Specified in MB without a measurement unit | |
| 51200 (in MB, i.e., 50 GB) | Specified in MB without a measurement unit | |
| 134217728 (in bytes) | Sizing for | Specified in bytes without a measurement unit |
|
| Setting Depending on whether your system runs only the CData Virtuality Server and the amount of system memory available, this may be preferable to on-heap allocation. The primary benefit is additional memory usage without additional garbage collection tuning. This becomes especially important in situations where more than 32 GB of memory is desired for the VM. Note that when using off-heap allocation, the memory must still be available to the java process and that setting the value of | |
|
| Determines how much memory exactly the server can use for buffers/ The default value buffer-service element of dvserver-standalone.xml | Specified in MB without a measurement unit |
In systems where extensive intermediate results are normal (scrolling cursors or sorting over millions of rows), you can consider increasing max-processing-kb
and decreasing max-reserve-kb
so that each request has access to an effectively smaller buffer space. Each intermediate result buffer, temporary LOB, and the temporary table are stored in their own set of buffer files, where an individual file is limited to max-file-size
megabytes. Consider increasing the storage space available to all such files if your installation uses internal materialization, makes heavy use of SQL/XML, or processes large row counts.
Recommendations
General Recommendations
Analytical Storage on | ||
---|---|---|
Setting | same | different |
host as DataVirtuality Server | ||
| 65–75 % of available RAM | 80–85 % of available RAM |
| 60% of | |
| 10 % of | 14 % of |
| yes, if | |
| 50 % of | |
| 256 MB RAM |
Example: Recommendations for a System with 32 GB of RAM
Analytical Storage on | ||
---|---|---|
Setting | same | different |
host as CData Virtuality Server | ||
| 20 GB | 27 GB |
| 12 GB | 16 GB |
| 512 MB | 768 MB |
|
|
|
| 10240 | 13312 |
| 256 MB |
See Also
Changing Directory of Temp Folder CData Virtuality Server のテンポラリフォルダの場所を変更する方法については、こちらをご覧ください。