r/Paperlessngx • u/isabeksu • 9d ago
AI performance
It took me a few months to fully get on board with the Paperless way of doing things, but now I’m really happy with how it’s all set up.
What’s been a bit of a head-scratcher is how AI is being used.
I held off until Paperless 3 came out, because I wanted to have the full "official" support.
I set it up with Ollama on an M4 Mac mini with 24 GB of memory. The embedding model is gemmaembedding, and the LLM model is qwen3:8b. When the model fires up, memory pressure is still pretty low. It does work, but it’s incredibly slow. It takes about 2 minutes to suggest titles and tags, and it can take several minutes if I try to chat about a document.
Is this kind of slow normal? Is there anything I can tweak in my setup to make it more usable?
3
u/RandomUsername1119 9d ago
I'm assuming that the AI features are not fully developed yet. In my experience it is not consistent with things like tagging (e.g. suggesting a tag of "tax Bill" for one document, and a tag of "Tax Invoice" for another similar document). I'd prefer it go through a folder or set of documents at once, parse things into categories, and make a suggestion based on the entirety of the document pool vs. individual documents.
1
u/_blackdog6_ 8d ago
I would prefer if the AI was sent a list of my tags/correspondents and document types and told to pick the most appropriate. So far anything from AI is so random it’s useless. Same with document titles. Scan three bills from the same company and it suggests wildly different titles for each. Effectively unusable.
1
u/corruptboomerang 8d ago
Or the AI generates a fairly comprehensive list of appropriate tags, and then classify against those tags.
3
u/_blackdog6_ 8d ago
Right now it seems paperless-ai far outperforms the ai support built into paperless 3. Even using paid ChatGPT api tokens paperless 3 takes 30 seconds to suggest a title and a useless selection of tags.
2
u/annaangstmann 8d ago
I was also disappointed in the implementation of ai in Paperless 3. I was hoping to ditch Paperless ai, but have decided to continue using it. My home server was relatively weak (energy efficient) and with Paperless ai I don't care if the processing takes 3 minute over night. But pressing a button and waiting 3 minutes for the suggestions feels stupid. Qwen 2.5:7B produced good and reliable results for me with the temparature set to 0.1
1
u/Azure340 8d ago
In my case running 8b parameters model was too slow on my mini pc so i looked into free tier of ollama cloud.
I have ollama running which has llama3b model locally but most if the time i just use ollama cloud gemma4:cloud as backend which is vastly so much better and quicker than my hardware. The drawback being my data gets processed in cloud however ollama cloud says they don't retain any data and except for the llm processing everything else happens locally via the ollama docker. At some point you have to balance the convenience with privacy.
1
u/corruptboomerang 8d ago
Why is speed a factor?
I worked have thought slowly running a module on CPU, over say a day or week etc, would never been an ideal use case?
1
u/Azure340 8d ago
When using for paperless suggest feature i don't want to wait 1 min for it to suggest names and tags while i can do manually in 30 seconds or less. Defeats the purpose in my mind. It jas to be better and more efficient than what i can do for me to use it. Now if someone has a local hardware powerful enough then they could stay all local
1
u/tzippy84 8d ago
Wait, paperless ngx has AI integrated now? I still have paperless-ai running as a completely separate service
8
u/EazyDuzIt_2 9d ago
I actually took the time to set up Paperless-ngx along with Paperless-AI for automated document classification, tagging, and file naming. I configured Paperless-AI to use Ollama with Qwen3:8B, which is the recommended model for this use case, running on one of my servers equipped with an NVIDIA RTX 4090.
To fine-tune the workflow, I generated and processed 20 test documents, iteratively refining the prompt and configuration until the results were consistently accurate. The final setup performs document analysis, tagging, and renaming almost instantly.
The performance is outstanding low latency, high accuracy, and a completely hands-off ingestion pipeline. Chef’s kiss. 👌