gwsystems / gwsystems/sledge-serverless-framework
How can I reproduce the concurrency result of the paper？
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 124
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
I try to run sledge to reproduce the concurrency result of the paper. But when worker core go with linear increasing, the throughput stay still.
I try to open some log commented out in Makefile or add some log to sledge, such as LOG_HTTP_PARSER, found that all work cores indeed do the computing. It seems like some critical resources can only allocate to these workers per unit time. It troubles me some time. I would be grateful if I could get some suggestions.
I do the experiment as such below:
Run sledge:
LD_LIBRARY_PATH="$(pwd):$LD_LIBRARY_PATH" ./sledgert ../experiments/concurrency/spec.json
In other termial,Run hey client:
experiment_client 127.0.0.1 /sledge-serverless-framework/runtime/experiments/concurrency/res
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 with experiments/concurrency/spec.json and the documented sledgert and experiment_client commands to reproduce the throughput result. Review the Makefile logging options and the mentioned LOG_HTTP_PARSER output, then determine whether the concurrency experiment's observed throughput matches the paper and document the cause or reproduction findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- 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