Repository navigation
Deprecate multi-poll dispatch getter/setter - #1088
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
/ok to test |
madsbk
left a comment
There was a problem hiding this comment.
Looks good but I think we should also log a deprecation warning when KVIKIO_REMOTE_IO_REACTOR_DISPATCH is set, saying that it is ignored and will be removed in the next release.
There was a problem hiding this comment.
Good catch. Cleaned up both the .hpp and .cpp files.
It makes sense to log a warning when the env var is set. Made the changes accordingly.
|
Sorry that I added you to the wrong PR @Matt711! |
|
Temporarily hold off on the merge, as @Matt711 may have observed that |
|
I ran SF-1K and SF-300, and I'm not able to reproduce. For SF-300 the numbers swing a lot: in the first pass, PER_CHUNK wins, whereas in the second pass SHARED_QUEUE wins. If we take the means, SHARED_QUEUE still wins slightly. |
|
Also ran SF-100 back to back multiple times. |
KvikIO rapidsai/kvikio#1088 makes the MULTI_POLL reactors always take work from one shared queue, and deprecates the reactor dispatch setting. kvikio.defaults.get/set("remote_io_reactor_dispatch") now emits a FutureWarning, and setting it has no effect. cudf-polars calls both whenever it configures KvikIO for a MULTI_POLL engine, which breaks the test suite under the `filterwarnings = error` setup. This PR removes the `kvikio_reactor_dispatch` executor option and its `CUDF_POLARS__EXECUTOR__KVIKIO_REACTOR_DISPATCH` environment variable, so cudf-polars no longer reads or sets the dispatch in KvikIO. This is a breaking change. Once #1088 is merged the option would have no effect anyway. Authors: - Tianyu Liu (https://github.com/kingcrimsontianyu) Approvers: - Tom Augspurger (https://github.com/TomAugspurger) URL: #24681
|
/merge |
This PR deprecates multi-poll's dispatch getter and setter and uses
SHARED_QUEUEuniversally. This will substantially simplify the current code and also simplify the batch API implementation.KVIKIO_REMOTE_IO_MAX_CONCURRENT_REQUESTS=0(unlimited) is still allowed, under which case each reactor takes at most an even share of the queue per pass.