multithreading support in librelp (or rsyslog relp input)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 32
- Forks
- 39
- Avg merge
- 2h 27m
- Merged PRs (30d)
- 7
Description
RELP input was eating 100% of single CPU core under my load (about 100k msg/s). It was unable to process message queue. So I switched to imptcp which able to run on multiple CPU cores. It'd be great if librelp (or imrelp) were able to run on multiple CPU cores.
If multithreading implementation is problematic it may be good enough to isolate at least every RELP input. Then it will be possible to start multiple inputs and spread load over them (using message sharding e.g.).
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 current RELP input processing in librelp and the rsyslog RELP input, then compare the reported behavior with imptcp. Done means RELP can process work across multiple CPU cores, or separate RELP inputs can be isolated so message sharding can distribute the load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100