itsgoingd / itsgoingd/clockwork
Feature: Imporve Cache Collector
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6k
- Forks
- 333
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
We ran a high-loaded project and it is very important to monitor how the application utilizes cache.
I'd suggest to collecting the size of the cache values, something like Str::length(serialize($query['value'])). It can be configurable feature.
Also, I'd suggest adding the option for hiding cache values itself but show key names (disabling the collect_queries option disables listing of cache keys as well).
In our server infrastructure bandwidth between the app and Redis servers is the bottleneck, so monitoring cache value sizes during development is very important.
If maintainers are ok with this, I can send PR.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the cache collector and the configuration behind the collect_queries option. Trace how cache keys and values are currently collected, then determine how the requested value-size reporting and hiding values should be represented and configured; done means the behavior is covered for both enabled and disabled collection modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php, redis
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100