| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Is apply_batched also in scope for this issue? And map/map_batched? |
Sorry, something went wrong.
| func: Callable[[BaseDocument], BaseDocument], | ||
| num_worker: Optional[int] = None, | ||
| pool: Optional['Pool'] = None, | ||
| show_progress: bool = False, |
There was a problem hiding this comment.
Should we have a backend options to switch between multi-processing and multi-threading?
Sorry, something went wrong.
There was a problem hiding this comment.
As far as I understood we only wanted to keep multiprocessing, not multithreading @samsja
Sorry, something went wrong.
There was a problem hiding this comment.
@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 a problem hiding this comment.
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.
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 a problem hiding this comment.
Looks good! We will make the map functions public, right?
Sorry, something went wrong.
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.
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
Signed-off-by: anna-charlotte <charlotte.gerhaher@jina.ai>
|
📝 Docs are deployed on https://ft-feat-map-apply--jina-docs.netlify.app 🎉 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Goals:
Add map_docs function and map_batch:
This will be different from doing
leverage multiprocessing by benchmarking in test, check that using 2 CPUS is faster then using 1
map_docs()
map_docs_batch()
benchmarking tests
check and update documentation, if required. See guide