aboutsummaryrefslogtreecommitdiffhomepage
path: root/patches/api/0457-Suspicious-Effect-Entry-API.patch
diff options
context:
space:
mode:
authorSpottedleaf <[email protected]>2024-06-03 13:28:31 -0700
committerSpottedleaf <[email protected]>2024-06-03 13:31:41 -0700
commit4f13be937eda5ee18010b271474a91894348e3e4 (patch)
tree2beb0d3d5a854c3155ea4a12b16ce5b36efb2575 /patches/api/0457-Suspicious-Effect-Entry-API.patch
parentb8f2101c3699763fc04e7a312f9b70539cbb873e (diff)
downloadPaper-4f13be937eda5ee18010b271474a91894348e3e4.tar.gz
Paper-4f13be937eda5ee18010b271474a91894348e3e4.zip
Do not perform chunk existance check for I/O scheduling
In order to check if a chunk exists, the RegionFile lock (if the RegionFile is opened) will be acquired. However, the RegionFile may be performing I/O operations, in which case will stall the acquire operation. To ensure that threads scheduling loads do not incur a stall, we can avoid this check entirely - the RegionFile I/O thread(s) will eventually perform the exist check itself.
Diffstat (limited to 'patches/api/0457-Suspicious-Effect-Entry-API.patch')
0 files changed, 0 insertions, 0 deletions