-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: parallel fetch #413
feat: parallel fetch #413
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks really good! I have just a few questions
} | ||
} | ||
|
||
const packages = this.storage.splice(0, this.limit); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good call on removing them from the array, mutating will indeed likely be the fastest here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually I'm still hesitating with having "named page" in a object
{ '0-100': [...], '100-200': [...] }
or with the nextKey { '@a/a': [...], '@a/ba': [...] }
this way we could fetch multiples pages in parallel and even process multiple pages in parallel
It has been ported to #656 |
packagesFetcher
It will prefetch at start and continuously fill a storage will we do
saveDocs()