Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Poor performance in MultiProcessCollector with frequently changing PIDs
See original GitHub issueI’m using django-prometheus in multiprocess mode, and I’ve noticed the time to fetch metrics increases the longer the server has been running. Currently I’ve got 5414 *.db files in prometheus_multiproc_dir.
MultiProcessCollector.collect reads all db files which I suspect is the bottleneck.
mark_process_dead only removes gauge files.
Do you think it’d be feasible to remove all files by copying the contents of type_{pid}.db files into a single type_old.db file? Or is this something that should be solved in django-prometheus?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is a relatively new feature, so there’s no specific guidance yet. I’d say balance the disruption of a restart against the cost of handling more data.
We are running into the same issue - is there a fix already?