starred/monolog
1
0
Fork 0
mirror of https://github.com/Seldaek/monolog.git synced 2026-04-26 08:05:53 +03:00
Code Issues 31 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #760] [Tech debt] Distributed batch proccesing #290

New issue
Closed
opened 2026-03-04 02:13:51 +03:00 by kerem · 2 comments
kerem commented 2026-03-04 02:13:51 +03:00
Owner
Copy link

Originally created by @ese on GitHub (Mar 31, 2016).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/760

We have now huge tasks like occupation feeds running in batch at once, This means they need a big amount of RAM to store objects while are proccesing which can have impact in the server performance.
This also avoid the possibility of distribute the load across different servers.

The thing should be divide the task in individual jobs that they can be queued and have differents process (workers) that can consume its

Originally created by @ese on GitHub (Mar 31, 2016). Original GitHub issue: https://github.com/Seldaek/monolog/issues/760 We have now huge tasks like occupation feeds running in batch at once, This means they need a big amount of RAM to store objects while are proccesing which can have impact in the server performance. This also avoid the possibility of distribute the load across different servers. The thing should be divide the task in individual jobs that they can be queued and have differents process (workers) that can consume its
kerem closed this issue 2026-03-04 02:13:51 +03:00
kerem commented 2026-03-04 02:13:52 +03:00
Author
Owner
Copy link

@xabbuh commented on GitHub (Mar 31, 2016):

Can you explain a bit how your problem is related to Monolog (which is a logging library)?

<!-- gh-comment-id:203974842 --> @xabbuh commented on GitHub (Mar 31, 2016): Can you explain a bit how your problem is related to Monolog (which is a logging library)?
kerem commented 2026-03-04 02:13:52 +03:00
Author
Owner
Copy link

@ese commented on GitHub (Mar 31, 2016):

oops sorry, I opened the issue in the wrong repository :(

<!-- gh-comment-id:203993661 --> @ese commented on GitHub (Mar 31, 2016): oops sorry, I opened the issue in the wrong repository :(
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
esfix
2.x
1.x
3.10.0
2.11.0
3.9.0
3.8.1
3.8.0
2.10.0
3.7.0
3.6.0
2.9.3
3.5.0
2.9.2
3.4.0
3.3.1
2.9.1
3.3.0
2.9.0
3.2.0
2.8.0
3.1.0
2.7.0
1.27.1
3.0.0
2.6.0
3.0.0-RC1
2.5.0
2.4.0
1.27.0
2.3.5
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
1.26.1
2.2.0
1.26.0
2.1.1
1.25.5
2.1.0
1.25.4
2.0.2
1.25.3
2.0.1
1.25.2
1.25.1
1.25.0
2.0.0
2.0.0-beta2
2.0.0-beta1
1.24.0
1.23.0
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.2
1.18.1
1.18.0
1.17.2
1.17.1
1.17.0
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.1
1.4.0
1.3.1
1.3.0
1.2.1
1.2.0
1.1.0
1.0.2
1.0.1
1.0.0
1.0.0-RC1
Labels
Clear labels   
Bug

   
Documentation

   
Feature

   
Needs Work

   
Support

   
pull-request

Mirrored from GitHub Pull Request

No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#290
No description provided.