Do not use OpenZGY write with default IOCONTEXT values
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
Use less memory hungry values for OpenZGY's iocontext setting. The old method of using default parameter would allow the OpenZGY write cache to grow up to 2GB for large files!
The parameters can now be tuned at run time. The operation now uses the following environment variables for the iocontext: SEGYTOZGY_IOCONTXT_BUFFER_SIZE <Default value is 32 MB> SEGYTOZGY_IOCONTXT_WRITE_THREADS <Default value is 16 threads> SEGYTOZGY_IOCONTXT_CPU_THREADS <Less critical parameter, default value is 1> SEGYTOZGY_IOCONTXT_IO_THREADS <Less critical parameter, default value is 1>
Using the new default values (i.e. not setting the environment variables) results in an OpenZGY cache size of (32 * 16) = 512Mb
Edited by Erik Dahl