GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||
GeezerVison is showing github.com — feat: add map function by anna-charlotte · Pull Request #1187 · docarray/docarray
This repository was archived by the owner on Sep 9, 2026. It is now read-only.
Conversation
|
|
Is |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| func: Callable[[BaseDocument], BaseDocument], | ||
| num_worker: Optional[int] = None, | ||
| pool: Optional['Pool'] = None, | ||
| show_progress: bool = False, |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should we have a backend options to switch between multi-processing and multi-threading?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
As far as I understood we only wanted to keep multiprocessing, not multithreading @samsja
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
@JoanFM maybe know more. But to me only multi processing makes sense. Can multi threading really improve performance here ?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Just the keep the PR discussion up to date with what we discussed on Discord: there will be multi threading since it makes sense for IO bound ops and tf/np/torch stuff
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Map is already included, but private right now. Not sure if we want to expose it again, or only one of the two. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
3a943a6 to
6c8176a
Compare
92d7a46 to
4c27409
Compare
There was an error while loading. Please reload this page.
9263bdb to
14e3cc1
Compare
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good! We will make the map functions public, right?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
c7bef8f to
a84b56d
Compare
I dont really have an opinion on this. @samsja suggested to keep only one of the two exposed, |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Why should we keep only one @samsja? I think both make sense, the user might already have an in-place or pure function that they want to use without rewriting |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
6a8b753 to
4a3a290
Compare
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Signed-off-by: anna-charlotte <[email protected]>
Signed-off-by: anna-charlotte <[email protected]>
|
📝 Docs are deployed on https://ft-feat-map-apply--jina-docs.netlify.app 🎉 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Map and apply with multiprocessing
There was an error while loading. Please reload this page.