litespeedtech / litespeedtech/lsmcd
Differences with Memcached: CACHESIZE and stats
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 39
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
New to lsmcd, wondering how to set/change the CACHESIZE as i would have done in `/etc/sysconfig/memcached` with memcached. It appears the default is set to 1024, but is it possible to change?
Also, `stats` command seems to differ from the memcached stats, where I get things like uptime, bytes read, etc.
lsmcd
```
Array
(
[pid] => 1459
[version] => 1.0.0
[pointer_size] => 64
[rusage_user] => 0.015967
[rusage_system] => 0.045063
[cmd_get] => 0
[cmd_set] => 124
[cmd_flush] => 0
[cmd_touch] => 0
[get_hits] => 0
[get_misses] => 0
[delete_misses] => 0
[delete_hits] => 4
[incr_misses] => 0
[incr_hits] => 0
[decr_misses] => 0
[decr_hits] => 0
[cas_misses] => 0
[cas_hits] => 0
[cas_badval] => 0
[touch_hits] => 0
[touch_misses] => 0
[auth_cmds] => 0
[auth_errors] => 0
)
```
memcached:
```
[pid] => 29178
[uptime] => 9120237
[time] => 1500575151
[version] => 1.4.4
[pointer_size] => 64
[rusage_user] => 67404.226999
[rusage_system] => 157157.292460
[curr_connections] => 20
[total_connections] => 306250738
[connection_structures] => 784
[cmd_get] => 8811703023
[cmd_set] => 887905901
[cmd_flush] => 0
[get_hits] => 8656932597
[get_misses] => 154770426
[delete_misses] => 14493
[delete_hits] => 31415
[incr_misses] => 128402148
[incr_hits] => 155504794
[decr_misses] => 0
[decr_hits] => 0
[cas_misses] => 0
[cas_hits] => 0
[cas_badval] => 0
[auth_cmds] => 0
[auth_errors] => 0
[bytes_read] => 2493081761115
[bytes_written] => 17308710353608
[limit_maxbytes] => 1073741824
[accepting_conns] => 1
[listen_disabled_num] => 0
[threads] => 4
[conn_yields] => 0
[bytes] => 95711633
[curr_items] => 102697
[total_items] => 733072550
[evictions] => 175005
```
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
No files, tests, or entry points are named. First locate how CACHESIZE is configured and where the stats response is produced, then clarify whether the expected outcome is documentation, configuration support, or additional metrics. Done requires a maintainer-confirmed scope and documented behavior or tests for the agreed changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, memcached
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100