commit | a877a724cc47dd269796a30bdf623814126b40af | [log] [tgz] |
---|---|---|
author | Paul J. Davis <davispa@us.ibm.com> | Mon Jun 29 15:24:23 2020 -0500 |
committer | Paul J. Davis <davispa@us.ibm.com> | Mon Jun 29 15:24:23 2020 -0500 |
tree | 7832eec6008b3ab72cb707980706e00a9970b297 | |
parent | c1ba0db845dd6e6c679558acb2bbe42ce64a26f4 [diff] |
Shed load in ioq_server This avoids processing any request that we find either in our message box or in our internal queuing system that has already timedout and had the client exit.
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.