This repository has been archived by the owner on Dec 26, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
howjmay
added
A-core
Area - Internals and/or core implementation
C-feature
Category - feature
labels
Mar 11, 2020
jserv
reviewed
Mar 11, 2020
jserv
suggested changes
Mar 11, 2020
howjmay
force-pushed
the
redis_cap
branch
4 times, most recently
from
March 13, 2020 02:22
7dc3532
to
c8a7192
Compare
Wait for the result in #525 |
howjmay
force-pushed
the
redis_cap
branch
3 times, most recently
from
May 5, 2020 03:30
51a880b
to
65a8e1f
Compare
Add high level descriptions about Redis-based caching in top-level documentation. |
howjmay
force-pushed
the
redis_cap
branch
3 times, most recently
from
May 5, 2020 07:50
36af64a
to
6b11701
Compare
jserv
reviewed
May 5, 2020
jserv
changed the title
feat(cache): Check cache database capacity
feat(cache): Check cache capacity
May 5, 2020
Caching is a buffering technique that stores frequently-queried data in a temporary memory. It makes data easier to be accessed and reduces workloads for databases. We usually say "database cache", which is indeed buffering something for database workload. However, "cache database" is not so meaningful. |
YingHan-Chen
suggested changes
May 18, 2020
Rebasing is required. |
jserv
reviewed
May 20, 2020
howjmay
force-pushed
the
redis_cap
branch
2 times, most recently
from
May 20, 2020 09:10
5c2d957
to
f248948
Compare
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
jserv
suggested changes
May 20, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SC_CACHE_LOCK and SC_CACHE_LOCK_ERROR are confusing
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
jserv
reviewed
May 20, 2020
`cache_occupied_space()` would return the used size in caching database. When the capacity of redis server exceeds the maximun capacity, the health_track thread will pop the oldest UUID and the corresponding bundle. To avoid data racing, at the moment that health track is cleaning redis server, all the other thread is not able to cache service. Add the Document for buffer service. close DLTcollab#488
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cache_occupied_space()
would return the used size in caching database.The default buffer maximum size is 170 MB.
When the capacity of redis server exceeds the maximun capacity, the
health_track thread will pop the oldest UUID and the corresponding
bundle.
To avoid data racing, at the moment that health track is cleaning
redis server, all the other thread is not able to to cache service.
Add the Document for buffer service.
close #488