Skip to content
Discussion options

You must be logged in to vote

Hello! Sorry for the very late reply, we will do our best in the future to be more on top of these.

We think this is a case of bad IO/compute interleaving (scheduling), or in other words the manner in which we perform IO-bound and compute-bound tasks are not scheduled by the runtime appropriately for such a large scale factor.

This specific benchmark is something we haven't really looked at yet so it isn't crazy that we perform badly here.

Apologies again for the late response! Please let us know if you have other questions.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by connortsui20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants