| commit | 41590f5847aa616f8e49f02154360bf7c41d5405 | [log] [tgz] |
|---|---|---|
| author | Jay Doane <jaydoane@apache.org> | Tue Nov 02 14:12:26 2021 -0700 |
| committer | Jay Doane <jaydoane@apache.org> | Tue Nov 02 14:12:26 2021 -0700 |
| tree | 1f5d04578ae8a6813976acf09c4f7fbc016de11e | |
| parent | 4843f3709b4be997cf8424c44f856523fd31b7d1 [diff] |
Replace app env with config Currently, `stats_db` and `interval` are obtained from vm.args file via `application:get_env/2`. This is surprising since IOQ already depends on the config application for most of it's configuration parameters. This changes where those configuration values are obtained from vm.args to .ini files.
The following are the list of IOQ classes:
One can configure an ioq bypass, which removes an IO class from prioritization, as below:
config:set("ioq.bypass", "view_update", "true")
Note that setting an IOQ bypass can effectively trump all other classes, especially in the case of an interactive bypass v. compaction. This can lead to high disk usage.
The priority for a class can also be set ala:
config:set("ioq", "compaction", "0.3")
Or globally, using snippet/rpc:
s:set_config("ioq", "compaction", "0.314", global)
rpc:multicall(config, set, ["ioq", "compaction", "0.217"])
As the interactive class is ‘everything else’ its priority cannot be directly set.