-
Notifications
You must be signed in to change notification settings - Fork 132
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
Docspell in Docker uses too much ressources while importing #2930
Comments
Hi, |
Thanks!
|
Yes, you are right. I had the problem that my Server was running out of RAM... sorry. |
Yes, it's the solr-container. As soon as the solr-container is started, CPU-Usage goes max. |
high cpu usage could be caused by too little memory, in this case the garbage collector would run very often and occupies the cpu significantly. i don't know if this applies to your case, if course |
Thanks for your Answer, eikek. VM is showing 8 GB available (free) memory. |
That sounds good, you might then want to assign more heap to solr and see if that makes a difference. |
Perfect. Seems to work. Thank you. Following set in Docker-Compose-File for SOLR: Now importing > 6000 Docs. |
Ok. Did not help. Solr is always crashing even with lot of memory. Now I added more memory for joex (as mentioned in Docspell-Documentation) and reduced Solr again and now it works. See what will happen ... stay tuned. |
Do you see any logs at solr (or the thing that crashes)? |
still importing > 6000 Docs :D When finished, I will setup the old config and give you more information. What I can say is, that Solr crashes (and docker restarts the container always because of unless-stopped), when joex needs the whole CPU-Ressources. |
I setup Docspell as documented. It starting and useable. As soon as I import documents (dsc) the whole setup uses always all ressources (CPU) as available (and more. Docker runs in a Proxmox-VM. The VM is then not really usable). How can I limit the ressources Docspell uses?
I am really interested in running Docspell and want to migrate from paperless-ngx (> 6000 Documents). But I can't get it running smoothly since 2 weeks :(
Thank you.
The text was updated successfully, but these errors were encountered: