Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-20 14:43:37 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1541] [FEAT]: Provide guidance on approximate document handling capability based on hardware #995

New Issue
Closed
opened 2026-02-22 18:22:34 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:22:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @OrcVole on GitHub (May 26, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1541

What would you like to see?

To many users, it might be helpful to have statement indicating approximately how many documents could be analysed at one time. Some hardware might be able to handle many more .pdf and .epub files than others. Also, providing some idea of how long it might take to ingest/upload a document might be reassuring, too.

Something like this, for example: If you have 8GB VRAM and 16GB RAM, then your device could probably handle one ebook.... If the ebook is about 200 pages and includes illustrations, it might take about 10 minutes to ingest.

Originally created by @OrcVole on GitHub (May 26, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1541 ### What would you like to see? To many users, it might be helpful to have statement indicating approximately how many documents could be analysed at one time. Some hardware might be able to handle many more .pdf and .epub files than others. Also, providing some idea of how long it might take to ingest/upload a document might be reassuring, too. Something like this, for example: If you have 8GB VRAM and 16GB RAM, then your device could probably handle one ebook.... If the ebook is about 200 pages and includes illustrations, it might take about 10 minutes to ingest.
yindo added the enhancementfeature request labels 2026-02-22 18:22:35 -05:00
yindo closed this issue 2026-02-22 18:22:35 -05:00
yindo commented 2026-02-22 18:22:35 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 26, 2024):

This is so dependent on hardware that benchmarking this would be a guesstimate at best, and flat out wrong at worst. This also depends on the specific document being collected. EPUBS, as you mentioned at more complex to parse than regular text files, but things like mp3/mp4 as insanely resource intensive as it runs a whole whipser model locally to make that work.

Its just too dependent on hardware, setup, RAM, and file types that makes documenting something like this so specifically a rabbithole. Obviously there is a standard window of time that is acceptable, but again that being resource dependent we would like to assume the user would be aware that parsing a 4K page PDF on a Raspberry Pi would not be instant!

@timothycarambat commented on GitHub (May 26, 2024): This is so dependent on hardware that benchmarking this would be a guesstimate at best, and flat out wrong at worst. This also depends on the specific document being collected. EPUBS, as you mentioned at more complex to parse than regular text files, but things like mp3/mp4 as insanely resource intensive as it runs a whole whipser model locally to make that work. Its just too dependent on hardware, setup, RAM, and file types that makes documenting something like this so specifically a rabbithole. Obviously there is a standard window of time that is acceptable, but again that being resource dependent we would like to assume the user would be aware that parsing a 4K page PDF on a Raspberry Pi would not be instant!
yindo changed title from [FEAT]: Provide guidance on approximate document handling capability based on hardware to [GH-ISSUE #1541] [FEAT]: Provide guidance on approximate document handling capability based on hardware 2026-06-05 14:38:21 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#995
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?