run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-26 16:56:36 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Process Time Inconsistent #322

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

Originally created by @tech-deployment on GitHub (Nov 6, 2024).

Originally assigned to: @BinaryBrain on GitHub.

Describe the bug
I am trying to understand why do I get so much difference to get a parsing response between:

  • Parse a file directly on LlamaCloud
  • Parse a file Using the Python Client

Job ID
JobId using LlamaCloud: 11d692d2-c10b-4323-a1b6-659ce705b9a6
JobId using LlamaParse Client: 27be0d32-3923-438b-b782-51fbf39e5695

Additional context
I have been using for both the same option:
-> Accurate Mode
-> Both are not using the cache

Some Numbers:
On LlamaCloud the average processing time is around 2/4 seconds.
Using LlamaParse python client I am getting an average of 26 seconds (when it complete sometime it's hang forever).

Is there any setup to be done on the Python Client to get up to speed?

Thank you

Pierre

Originally created by @tech-deployment on GitHub (Nov 6, 2024). Originally assigned to: @BinaryBrain on GitHub. **Describe the bug** I am trying to understand why do I get so much difference to get a parsing response between: - Parse a file directly on LlamaCloud - Parse a file Using the Python Client **Job ID** JobId using LlamaCloud: 11d692d2-c10b-4323-a1b6-659ce705b9a6 JobId using LlamaParse Client: 27be0d32-3923-438b-b782-51fbf39e5695 **Additional context** I have been using for both the same option: -> Accurate Mode -> Both are not using the cache **Some Numbers:** On LlamaCloud the average processing time is around 2/4 seconds. Using LlamaParse python client I am getting an average of 26 seconds (when it complete sometime it's hang forever). Is there any setup to be done on the Python Client to get up to speed? Thank you Pierre
yindo added the bug label 2026-02-16 00:17:28 -05:00
yindo commented 2026-02-16 00:17:29 -05:00
Author
Owner
Copy Link
Copy Source

@galvangoh commented on GitHub (Nov 6, 2024):

I am also using the python client. For my set up, I am using multimodal with instructions and no caches. I have been trying to shorten my instructions however recently it seems the service is getting rather unstable in the processing time. My run can take up to 10 mins for a document of a few pages.

@galvangoh commented on GitHub (Nov 6, 2024): I am also using the python client. For my set up, I am using multimodal with instructions and no caches. I have been trying to shorten my instructions however recently it seems the service is getting rather unstable in the processing time. My run can take up to 10 mins for a document of a few pages.
yindo commented 2026-02-16 00:17:29 -05:00
Author
Owner
Copy Link
Copy Source

@BinaryBrain commented on GitHub (Nov 7, 2024):

Hi Pierre,
In our pod doing the actual processing of the file, I see:

00:12:58.441 Processing job job_record_id: 11d692d2-c10b-4323-a1b6-659ce705b9a6
00:13:22.149 [job_record_id=11d692d2-c10b-4323-a1b6-659ce705b9a6] job result done

There's no way you can have a non-cached result in 2-4 seconds in accurate mode. (Although I wish it was the case).
26 seconds seems reasonable. Please send me your JobID when the job hangs forever.

@BinaryBrain commented on GitHub (Nov 7, 2024): Hi Pierre, In our pod doing the actual processing of the file, I see: ``` 00:12:58.441 Processing job job_record_id: 11d692d2-c10b-4323-a1b6-659ce705b9a6 00:13:22.149 [job_record_id=11d692d2-c10b-4323-a1b6-659ce705b9a6] job result done ``` There's no way you can have a non-cached result in 2-4 seconds in accurate mode. (Although I wish it was the case). 26 seconds seems reasonable. Please send me your JobID when the job hangs forever.
yindo commented 2026-02-16 00:17:29 -05:00
Author
Owner
Copy Link
Copy Source

@davidrzs commented on GitHub (Nov 13, 2024):

Can confirm this the stark increase in processing times. Today it was quite slow that downstream calls (internal to our code) started to time out.

@davidrzs commented on GitHub (Nov 13, 2024): Can confirm this the stark increase in processing times. Today it was quite slow that downstream calls (internal to our code) started to time out.
yindo commented 2026-02-16 00:17:29 -05:00
Author
Owner
Copy Link
Copy Source

@pierre-sigwalt commented on GitHub (Nov 14, 2024):

The Job Id that was hanging for a very long time was:
27be0d32-3923-438b-b782-51fbf39e5695 (If I remember, I will have to test again in order to see).

@pierre-sigwalt commented on GitHub (Nov 14, 2024): The Job Id that was hanging for a very long time was: 27be0d32-3923-438b-b782-51fbf39e5695 (If I remember, I will have to test again in order to see).
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#322
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?