Skip to content
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

Document how incorrectly creating schedulers can cause excessive network usage #860

Open
Balearica opened this issue Dec 16, 2023 · 0 comments · May be fixed by #866
Open

Document how incorrectly creating schedulers can cause excessive network usage #860

Balearica opened this issue Dec 16, 2023 · 0 comments · May be fixed by #866

Comments

@Balearica
Copy link
Collaborator

When workers are created one at a time for a scheduler, Chrome downloads the code and lang data once for the first worker, and then uses the cached version for the later workers. However, if multiple workers are created in parallel (and the data is not already cached), Chrome appears to download new data for every worker. This could cause significant issues--inflating data usage for mobile users and significantly slowing down Tesseract.js initialization times for users with slow connections. This should be explained in the documentation.

Asadullahkhankaimkhani added a commit to Asadullahkhankaimkhani/tesseract.js that referenced this issue Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant