Replies: 2 comments 1 reply
-
|
@mbasmanova would you please have a look at this question ? many thanks |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Guys,
I noticed the introduction of LazyVector in Velox, along with its related code implementation. The design concept of LazyVector is excellent; it employs lazy loading to only fetch the necessary rows of data as needed during expression evaluation, thereby minimizing I/O as much as possible.
However, I find it somewhat odd that, the loading process for LazyVector is synchronous, whereas data loading by the connector is generally performed asynchronously from storage. Moreover, since expression execution occurs on threads rather than coroutines, this synchronous calling can continuously occupy thread resources when encountering I/O wait.
Is this current approach viable? Or are there any other techniques or considerations to take into account when using it?
Beta Was this translation helpful? Give feedback.
All reactions