How to improve the set/delete performance?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
We use evcache with one memcache server node. We find there are much EVCache.set/delete operations which need more than 500ms.
I'm not sure if the performance is up to the limitation. Here are some monitor log.
Key total number in memcache: 700k
QPS: 400 to 600
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 reviewing the EVCache set/delete request path and the provided monitor figures: 700k keys, 400–600 QPS, and operations exceeding 500ms. The issue names no files, tests, or specific expected change; done would require identifying the cause of the latency and defining a reproducible performance improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, memcached
- Domain
- distributed-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100