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

[GH-ISSUE #883] [FEAT]: Push event logging to asynchronous tasks #528

New Issue
Closed
opened 2026-02-22 18:19:58 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:19:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @khareyash05 on GitHub (Mar 10, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/883

What would you like to see?

I had been going through the server side code and I found out that event logging functionalities in api can cause critical tasks like new admin creation to fail if they take a lot of time. Pushing those events to a message queue system can enable critical tasks to complete without any hinderance thus also enabling easy scaling .

I can help implement the system using BullMQ/ RabbitMQ/ Any other message brokers

Originally created by @khareyash05 on GitHub (Mar 10, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/883 ### What would you like to see? I had been going through the server side code and I found out that event logging functionalities in api can cause critical tasks like new admin creation to fail if they take a lot of time. Pushing those events to a message queue system can enable critical tasks to complete without any hinderance thus also enabling easy scaling . I can help implement the system using BullMQ/ RabbitMQ/ Any other message brokers
yindo added the enhancementfeature request labels 2026-02-22 18:19:58 -05:00
yindo closed this issue 2026-02-22 18:19:58 -05:00
yindo commented 2026-02-22 18:19:58 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 11, 2024):

The restriction here is that we cannot run any extra services that arent nodejs as we cannot port that to the desktop app.

Agreed that these tasks should not be blocking and be delegated to another service so that they are non-blocking.

@timothycarambat commented on GitHub (Mar 11, 2024): The restriction here is that we cannot run any extra services that arent nodejs as we cannot port that to the desktop app. Agreed that these tasks should not be blocking and be delegated to another service so that they are non-blocking.
yindo commented 2026-02-22 18:19:58 -05:00
Author
Owner
Copy Link
Copy Source

@khareyash05 commented on GitHub (Mar 12, 2024):

We have to find alternatives as it might cause major issues while scaling. I will look for alternative solutions if any.

@khareyash05 commented on GitHub (Mar 12, 2024): We have to find alternatives as it might cause major issues while scaling. I will look for alternative solutions if any.
yindo commented 2026-02-22 18:19:58 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 12, 2024):

I would suspect the bottleneck at any nominal scale would not be a DB call to a local DB file. It would likely be the LLM running inferencing. We have instances that have 100+ concurrent users with no hiccups and their slowest (or most costly) bottleneck is having an LLM provider that can manage that much throughput from users.

I still agree this should be moved to another process, but I really dont think this would be the bottleneck to be optimizing on

@timothycarambat commented on GitHub (Mar 12, 2024): I would suspect the bottleneck at any nominal scale would not be a DB call to a local DB file. It would likely be the LLM running inferencing. We have instances that have 100+ concurrent users with no hiccups and their slowest (or most costly) bottleneck is having an LLM provider that can manage that much throughput from users. I still agree this should be moved to another process, but I really dont think this would be the bottleneck to be optimizing on
yindo changed title from [FEAT]: Push event logging to asynchronous tasks to [GH-ISSUE #883] [FEAT]: Push event logging to asynchronous tasks 2026-06-05 14:35:48 -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#528
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?