Performance review (eprof) - WIP
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 54
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Some notes and potential performance-related issues to be based on eprof analysis.
Method:
- Run isolated perf_SUITE profiles to confirm performance profiles of certain functions at a vnode level.
- Run the [general_api_perf)[https://github.com/OpenRiak/riak_test/blob/openriak-3.4/tests/general_api_perf.erl] riak_test test, but with a more balanced load (more GETs), and as a multi-node cluster. Point all clients at the same node in the cluster.
- Periodically check eprof profiles on the client-connected node, and on a sample other node - to distinguish between API and object FSM load and backend load.
- Repeat with different settings to try and understand the profile.
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 the isolated perf_SUITE profiles and tests/general_api_perf.erl, then review the eprof profiling method for the client-connected and other cluster nodes under balanced GET-heavy load. The issue is WIP and does not define a concrete completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, distributed-systems, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100