memcached / memcached/mcshredder
Initial TODO
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
To give followers an idea of what's planned-ish, in rough priority order.
- request and response tokenizers, splitters, convenience functions
- more command generators (with/without numeric, vary key length, missing commands, etc)
-
mcs.out(message)for printing data instead of lua's print - add a listener to filter the output from mcs.out()
- automatically add meta Opaque tags on request generation, used with match below
-
local status, elapsed = mcs.match(request, response): does the response match the request and how long did it take - item value validation (using a hash of the key for the value data)
- rate pace randomization
- reconnect pace randomization
- tick the pacer on every write call instead of every return (ie; write two requests in one loop, counts twice toward limit)
- pcrg randomizer
- random length key string (similar to mctester)
- ramp up new connections over time
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
This issue is a broad, old TODO list and names no files, tests, or entry points. Start by selecting one unchecked item, then locate the relevant existing implementation and define the expected behavior before making a change; done means that single item is implemented and its behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100