Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My problem: i have many servers do caching data from key-value database. These caching data is frequently updated, then saved back to db. Consequently, the saved data is not the newest one, and i got data missed with high rate.
In my app, performance is more important, missing data is acceptable with low rate.
What’s the name of this problem (keyword) and your solution/strategy for it?
Thanks,
At low levels this is called the problem of ‘Dirty pages’.
There can be 2 issues, old data or no data in db compared to the data in cache. So depending on how much latency the application can afford, you should set the interval at which cache should be flushed to db.