Package org.bytedeco.hdf5

Class H5AC_cache_config_t

    • Constructor Detail

      • H5AC_cache_config_t

        public H5AC_cache_config_t()
        Default native constructor.

      • H5AC_cache_config_t

        public H5AC_cache_config_t​(long size)
        Native array allocator. Access with Pointer.position(long).

      • H5AC_cache_config_t

        public H5AC_cache_config_t​(Pointer p)
        Pointer cast constructor. Invokes Pointer(Pointer).

    • Method Detail

      • version

        public int version()
        Integer field indicating the the version of the H5AC_cache_config_t in use. This field should be set to #H5AC__CURR_CACHE_CONFIG_VERSION (defined in H5ACpublic.h).

      • rpt_fcn_enabled

        @Cast("hbool_t")
public boolean rpt_fcn_enabled()
        Boolean flag indicating whether the adaptive cache resize report function is enabled. This field should almost always be set to disabled (0). Since resize algorithm activity is reported via stdout, it MUST be set to disabled (0) on Windows machines.\n The report function is not supported code, and can be expected to change between versions of the library. Use it at your own risk.

      • open_trace_file

        @Cast("hbool_t")
public boolean open_trace_file()
        Boolean field indicating whether the \ref H5AC_cache_config_t.trace_file_name "trace_file_name" field should be used to open a trace file for the cache.\n The trace file is a debugging feature that allows the capture of top level metadata cache requests for purposes of debugging and/or optimization. This field should normally be set to 0, as trace file collection imposes considerable overhead.\n This field should only be set to 1 when the \ref H5AC_cache_config_t.trace_file_name "trace_file_name" contains the full path of the desired trace file, and either there is no open trace file on the cache, or the \ref H5AC_cache_config_t.close_trace_file "close_trace_file" field is also 1.\n The trace file feature is unsupported unless used at the direction of The HDF Group. It is intended to allow The HDF Group to collect a trace of cache activity in cases of occult failures and/or poor performance seen in the field, so as to aid in reproduction in the lab. If you use it absent the direction of The HDF Group, you are on your own.

      • close_trace_file

        @Cast("hbool_t")
public boolean close_trace_file()
        Boolean field indicating whether the current trace file (if any) should be closed.\n See the above comments on the \ref H5AC_cache_config_t.open_trace_file "open_trace_file" field. This field should be set to 0 unless there is an open trace file on the cache that you wish to close.\n The trace file feature is unsupported unless used at the direction of The HDF Group. It is intended to allow The HDF Group to collect a trace of cache activity in cases of occult failures and/or poor performance seen in the field, so as to aid in reproduction in the lab. If you use it absent the direction of The HDF Group, you are on your own.

      • trace_file_name

        @Cast("char")
public byte trace_file_name​(int i)
        Full path of the trace file to be opened if the \ref H5AC_cache_config_t.open_trace_file "open_trace_file" field is set to 1.\n In the parallel case, an ascii representation of the MPI rank of the process will be appended to the file name to yield a unique trace file name for each process.\n The length of the path must not exceed #H5AC__MAX_TRACE_FILE_NAME_LEN characters.\n The trace file feature is unsupported unless used at the direction of The HDF Group. It is intended to allow The HDF Group to collect a trace of cache activity in cases of occult failures and/or poor performance seen in the field, so as to aid in reproduction in the lab. If you use it absent the direction of The HDF Group, you are on your own.

      • evictions_enabled

        @Cast("hbool_t")
public boolean evictions_enabled()
        A boolean flag indicating whether evictions from the metadata cache are enabled. This flag is initially set to enabled (1).\n In rare circumstances, the raw data throughput quirements may be so high that the user wishes to postpone metadata writes so as to reserve I/O throughput for raw data. The \p evictions_enabled field exists to allow this. However, this is an extreme step, and you have no business doing it unless you have read the User Guide section on metadata caching, and have considered all other options carefully.\n The \p evictions_enabled field may not be set to disabled (0) unless all adaptive cache resizing code is disabled via the \ref H5AC_cache_config_t.incr_mode "incr_mode", \ref H5AC_cache_config_t.flash_incr_mode "flash_incr_mode", \ref H5AC_cache_config_t.decr_mode "decr_mode" fields.\n When this flag is set to disabled (\c 0), the metadata cache will not attempt to evict entries to make space for new entries, and thus will grow without bound.\n Evictions will be re-enabled when this field is set back to \c 1. This should be done as soon as possible.

      • set_initial_size

        @Cast("hbool_t")
public boolean set_initial_size()
        Boolean flag indicating whether the cache should be created with a user specified initial size.

      • initial_size

        @Cast("size_t")
public long initial_size()
        If \ref H5AC_cache_config_t.set_initial_size "set_initial_size" is set to 1, \p initial_size must contain he desired initial size in bytes. This value must lie in the closed interval [ \p min_size, \p max_size ]. (see below)

      • min_clean_fraction

        public double min_clean_fraction()
        This field specifies the minimum fraction of the cache that must be kept either clean or empty.\n The value must lie in the interval [0.0, 1.0]. 0.01 is a good place to start in the serial case. In the parallel case, a larger value is needed -- see the overview of the metadata cache in the “Metadata Caching in HDF5” section of the -- \ref UG for details.

      • max_size

        @Cast("size_t")
public long max_size()
        Upper bound (in bytes) on the range of values that the adaptive cache resize code can select as the maximum cache size.

      • min_size

        @Cast("size_t")
public long min_size()
        Lower bound (in bytes) on the range of values that the adaptive cache resize code can select as the minimum cache * size.

      • epoch_length

        public long epoch_length()
        Number of cache accesses between runs of the adaptive cache resize code. 50,000 is a good starting number.

      • incr_mode

        @Cast("H5C_cache_incr_mode")
public int incr_mode()
        Enumerated value indicating the operational mode of the automatic cache size increase code. At present, only two values listed in #H5C_cache_incr_mode are legal.

      • lower_hr_threshold

        public double lower_hr_threshold()
        Hit rate threshold used by the hit rate threshold cache size increment algorithm.\n When the hit rate over an epoch is below this threshold and the cache is full, the maximum size of the cache is multiplied by increment (below), and then clipped as necessary to stay within \p max_size, and possibly \p max_increment.\n This field must lie in the interval [0.0, 1.0]. 0.8 or 0.9 is a good place to start.

      • increment

        public double increment()
        Factor by which the hit rate threshold cache size increment algorithm multiplies the current cache max size to obtain a tentative new cache size.\n The actual cache size increase will be clipped to satisfy the \p max_size specified in the general configuration, and possibly max_increment below.\n The parameter must be greater than or equal to 1.0 -- 2.0 is a reasonable value.\n If you set it to 1.0, you will effectively disable cache size increases.

      • apply_max_increment

        @Cast("hbool_t")
public boolean apply_max_increment()
        Boolean flag indicating whether an upper limit should be applied to the size of cache size increases.

      • max_increment

        @Cast("size_t")
public long max_increment()
        Maximum number of bytes by which cache size can be increased in a single step -- if applicable.

      • flash_incr_mode

        @Cast("H5C_cache_flash_incr_mode")
public int flash_incr_mode()
        Enumerated value indicating the operational mode of the flash cache size increase code. At present, only two listed values in #H5C_cache_flash_incr_mode are legal.

      • flash_multiple

        public double flash_multiple()
        The factor by which the size of the triggering entry / entry size increase is multiplied to obtain the initial cache size increment. This increment may be reduced to reflect existing free space in the cache and the \p max_size field above.\n The parameter must lie in the interval [0.0, 1.0]. 0.1 or 0.05 is a good place to start.\n At present, this field must lie in the range [0.1, 10.0].

      • flash_threshold

        public double flash_threshold()
        The factor by which the current maximum cache size is multiplied to obtain the minimum size entry / entry size increase which may trigger a flash cache size increase. \n At present, this value must lie in the range [0.1, 1.0].

      • decr_mode

        @Cast("H5C_cache_decr_mode")
public int decr_mode()
        Enumerated value indicating the operational mode of the tomatic cache size decrease code. At present, the values listed in #H5C_cache_decr_mode are legal.

      • upper_hr_threshold

        public double upper_hr_threshold()
        Hit rate threshold for the hit rate threshold and ageout with hit rate threshold cache size decrement algorithms.\n When \p decr_mode is #H5C_decr__threshold, and the hit rate over a given epoch exceeds the supplied threshold, the current maximum cache size is multiplied by decrement to obtain a tentative new (and smaller) maximum cache size.\n When \p decr_mode is #H5C_decr__age_out_with_threshold, there is no attempt to find and evict aged out entries unless the hit rate in the previous epoch exceeded the supplied threshold.\n This field must lie in the interval [0.0, 1.0].\n For #H5C_incr__threshold, .9995 or .99995 is a good place to start.\n For #H5C_decr__age_out_with_threshold, .999 might be more useful.

      • decrement

        public double decrement()
        In the hit rate threshold cache size decrease algorithm, this parameter contains the factor by which the current max cache size is multiplied to produce a tentative new cache size.\n The actual cache size decrease will be clipped to satisfy the \ref H5AC_cache_config_t.min_size "min_size" specified in the general configuration, and possibly \ref H5AC_cache_config_t.max_decrement "max_decrement".\n The parameter must be be in the interval [0.0, 1.0].\n If you set it to 1.0, you will effectively disable cache size decreases. 0.9 is a reasonable starting point.

      • apply_max_decrement

        @Cast("hbool_t")
public boolean apply_max_decrement()
        Boolean flag indicating ether an upper limit should be applied to the size of cache size decreases.

      • max_decrement

        @Cast("size_t")
public long max_decrement()
        Maximum number of bytes by which the maximum cache size can be decreased in any single step -- if applicable.

      • epochs_before_eviction

        public int epochs_before_eviction()
        In the ageout based cache size reduction algorithms, this field contains the minimum number of epochs an entry must remain unaccessed in cache before the cache size reduction algorithm tries to evict it. 3 is a reasonable value.

      • apply_empty_reserve

        @Cast("hbool_t")
public boolean apply_empty_reserve()
        Boolean flag indicating whether the ageout based decrement algorithms will maintain a empty reserve when decreasing cache size.

      • empty_reserve

        public double empty_reserve()
        Empty reserve as a fraction maximum cache size if applicable.\n When so directed, the ageout based algorithms will not decrease the maximum cache size unless the empty reserve can be met.\n The parameter must lie in the interval [0.0, 1.0]. 0.1 or 0.05 is a good place to start.

      • dirty_bytes_threshold

        @Cast("size_t")
public long dirty_bytes_threshold()
        Threshold number of bytes of dirty metadata generation for triggering synchronizations of the metadata caches serving the target file in the parallel case.\n Synchronization occurs whenever the number of bytes of dirty metadata created since the last synchronization exceeds this limit.\n This field only applies to the parallel case. While it is ignored elsewhere, it can still draw a value out of bounds error.\n It must be consistent across all caches on any given file.\n By default, this field is set to 256 KB. It shouldn't be more than half the current max cache size times the min clean fraction.

      • metadata_write_strategy

        public int metadata_write_strategy()
        Desired metadata write strategy. The valid values for this field are:\n #H5AC_METADATA_WRITE_STRATEGY__PROCESS_0_ONLY: Specifies the only process zero is allowed to write dirty metadata to disk.\n #H5AC_METADATA_WRITE_STRATEGY__DISTRIBUTED: Specifies that process zero still makes the decisions as to what entries should be flushed, but the actual flushes are distributed across the processes in the computation to the extent possible.\n The src/H5ACpublic.h include file in the HDF5 library has detailed information on each strategy.