run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-18 15:54:38 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Issue with LlamaParse ...The API is suddently extremely slow in terms of responding to documents. Initially, my website used to get a response in seconds. Anyone felt the same? Thanks #406

New Issue
Open
opened 2026-02-16 00:17:45 -05:00 by yindo · 17 comments
yindo commented 2026-02-16 00:17:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @jayantsharma279 on GitHub (Jan 21, 2025).

Describe the bug
Write a concise description of what the bug is.

Files
If possible, please provide the PDF file causing the issue.

Job ID
If you have it, please provide the ID of the job you ran.
You can find it here: https://cloud.llamaindex.ai/parse in the "History" tab.

Client:
Please remove untested options:

  • Python Library
  • API
  • Frontend (cloud.llamaindex.ai)
  • Typescript Library
  • Notebook

Additional context
Add any additional context about the problem here.
What options did you use? Premium mode, multimodal, fast mode, parsing instructions, etc.
Screenshots, code snippets, etc.

Originally created by @jayantsharma279 on GitHub (Jan 21, 2025). **Describe the bug** Write a concise description of what the bug is. **Files** If possible, please provide the PDF file causing the issue. **Job ID** If you have it, please provide the ID of the job you ran. You can find it here: https://cloud.llamaindex.ai/parse in the "History" tab. **Client:** Please remove untested options: - Python Library - API - Frontend (cloud.llamaindex.ai) - Typescript Library - Notebook **Additional context** Add any additional context about the problem here. What options did you use? Premium mode, multimodal, fast mode, parsing instructions, etc. Screenshots, code snippets, etc.
yindo added the bug label 2026-02-16 00:17:45 -05:00
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@toludev3 commented on GitHub (Jan 22, 2025):

were you able to solve this, also just started experincing this yesterday. Takes alot of minute now

@toludev3 commented on GitHub (Jan 22, 2025): were you able to solve this, also just started experincing this yesterday. Takes alot of minute now
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@jayantsharma279 commented on GitHub (Jan 22, 2025):

A tad bit of improvement, not the usual speed like it was a few days back.

@jayantsharma279 commented on GitHub (Jan 22, 2025): A tad bit of improvement, not the usual speed like it was a few days back.
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@hamzanouali42 commented on GitHub (Jan 23, 2025):

I confirm that the issue is still there, not fixed yet. One of our 10MB documents took hours to finish.

@hamzanouali42 commented on GitHub (Jan 23, 2025): I confirm that the issue is still there, not fixed yet. One of our 10MB documents took hours to finish.
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@jasontjahjono commented on GitHub (Jan 27, 2025):

is there any updates to this?

@jasontjahjono commented on GitHub (Jan 27, 2025): is there any updates to this?
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@sandroxavierdeveloper commented on GitHub (Jan 29, 2025):

I am writing to report a significant decrease in performance with the LlamaParse API. Until this morning, the API consistently processed my documents within seconds. However, as of this evening, I am experiencing an abnormal delay in processing times.

To illustrate the issue, a 1-page document that previously took only seconds to process now takes 67 minutes. The document in question is a simple text file with no unusual formatting or complex elements. It uses a standard Arial font.

This performance degradation is significantly impacting my workflow, as I am currently in the testing phase of a project and rely heavily on LlamaParse for efficient document processing.

I have attached the Job ID for your reference: a313b44a-c542-453a-8db5-fea0d9631b0a

I would appreciate it if you could investigate this issue and provide a solution as soon as possible. Please let me know if you require any further information from my end.

@sandroxavierdeveloper commented on GitHub (Jan 29, 2025): I am writing to report a significant decrease in performance with the LlamaParse API. Until this morning, the API consistently processed my documents within seconds. However, as of this evening, I am experiencing an abnormal delay in processing times. To illustrate the issue, a 1-page document that previously took only seconds to process now takes 67 minutes. The document in question is a simple text file with no unusual formatting or complex elements. It uses a standard Arial font. This performance degradation is significantly impacting my workflow, as I am currently in the testing phase of a project and rely heavily on LlamaParse for efficient document processing. I have attached the Job ID for your reference: a313b44a-c542-453a-8db5-fea0d9631b0a I would appreciate it if you could investigate this issue and provide a solution as soon as possible. Please let me know if you require any further information from my end.
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@BharathxD commented on GitHub (Jan 31, 2025):

The same is happening with our workflows. They have been slow for the last 2 weeks, and the performance has been degraded. Somehow, the files are now taking more than 3-4 minutes, whereas they usually took 30-40 seconds.

@BharathxD commented on GitHub (Jan 31, 2025): The same is happening with our workflows. They have been slow for the last 2 weeks, and the performance has been degraded. Somehow, the files are now taking more than 3-4 minutes, whereas they usually took 30-40 seconds.
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@BinaryBrain commented on GitHub (Feb 5, 2025):

Hi @BharathxD
Do you have a jobID for a job that took 3-4 minutes?

@BinaryBrain commented on GitHub (Feb 5, 2025): Hi @BharathxD Do you have a jobID for a job that took 3-4 minutes?
yindo commented 2026-02-16 00:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@Liboul commented on GitHub (Feb 8, 2025):

Hi @BharathxD Do you have a jobID for a job that took 3-4 minutes?

Same issue, here's an example, this is a one-page simple PDF with text only: 02c05083-fbb1-4fcf-b7b9-973d3f6ba2c1
It used to take a couple of seconds, now it's around 100x that 😅

@Liboul commented on GitHub (Feb 8, 2025): > Hi [@BharathxD](https://github.com/BharathxD) Do you have a jobID for a job that took 3-4 minutes? Same issue, here's an example, this is a one-page simple PDF with text only: 02c05083-fbb1-4fcf-b7b9-973d3f6ba2c1 It used to take a couple of seconds, now it's around 100x that 😅
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@auktgs commented on GitHub (Feb 10, 2025):

Same issue here, its basically unusable.
Edit-> I turned off premium mode and its working ok now
Edit->slowed down again

@auktgs commented on GitHub (Feb 10, 2025): Same issue here, its basically unusable. Edit-> I turned off premium mode and its working ok now Edit->slowed down again
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@goharShoukat commented on GitHub (Feb 13, 2025):

I have a one page pdf with pure text. It's taking ages just to get the job started, let alone finishing it.

@goharShoukat commented on GitHub (Feb 13, 2025): I have a one page pdf with pure text. It's taking ages just to get the job started, let alone finishing it.
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@GoffAC commented on GitHub (Feb 15, 2025):

Seriously considering moving away from llama parse because of this. Most recently I have had a 17kb .docx that has taken 2.5 minutes to parse to markdown. What has happened?

Anyone moved already or has collected options and wants to share?

@GoffAC commented on GitHub (Feb 15, 2025): Seriously considering moving away from llama parse because of this. Most recently I have had a 17kb .docx that has taken 2.5 minutes to parse to markdown. What has happened? Anyone moved already or has collected options and wants to share?
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@BinaryBrain commented on GitHub (Feb 15, 2025):

Hey @GoffAC,
We've had a few issues when some specific conditions where met.
We released a patch yesterday that should fix this issue.
When did your issue occurred?

@BinaryBrain commented on GitHub (Feb 15, 2025): Hey @GoffAC, We've had a few issues when some specific conditions where met. We released a patch yesterday that should fix this issue. When did your issue occurred?
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@GoffAC commented on GitHub (Feb 15, 2025):

Hey @GoffAC,
We've had a few issues when some specific conditions where met.
We released a patch yesterday that should fix this issue.
When did your issue occurred?

Thanks for reaching out. 30 minutes ago. I can share details if needed?

@GoffAC commented on GitHub (Feb 15, 2025): > Hey @GoffAC, > We've had a few issues when some specific conditions where met. > We released a patch yesterday that should fix this issue. > When did your issue occurred? Thanks for reaching out. 30 minutes ago. I can share details if needed?
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@mehwishh247 commented on GitHub (Feb 18, 2025):

The issue is still there. The performance is quite slow even for a 1mb file. Along with this, there is an issue with reading guidelines as well. I have shared it in #620

@mehwishh247 commented on GitHub (Feb 18, 2025): The issue is still there. The performance is quite slow even for a 1mb file. Along with this, there is an issue with reading guidelines as well. I have shared it in #620
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@justme409 commented on GitHub (Mar 3, 2025):

yeah extremely slow for me too. unusable.

@justme409 commented on GitHub (Mar 3, 2025): yeah extremely slow for me too. unusable.
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@r3rer3 commented on GitHub (Jun 10, 2025):

yea same here. it is a bit random. for the same file, it sometimes takes a long time, and sometimes it does not.

@r3rer3 commented on GitHub (Jun 10, 2025): yea same here. it is a bit random. for the same file, it sometimes takes a long time, and sometimes it does not.
yindo commented 2026-02-16 00:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@DillonOLeary commented on GitHub (Jul 15, 2025):

Also having the same problem. It's becoming a big deal when using LlamaCloud tools. I just uploaded like 4 small markdown files to index dcb7882c-ce47-42d1-84a7-8bfabc59abf3 and now I'm on the second hour of waiting for them to process

@DillonOLeary commented on GitHub (Jul 15, 2025): Also having the same problem. It's becoming a big deal when using LlamaCloud tools. I just uploaded like 4 small markdown files to index dcb7882c-ce47-42d1-84a7-8bfabc59abf3 and now I'm on the second hour of waiting for them to process
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label bug
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: run-llama/llama_cloud_services#406
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?