tarantool / tarantool/tarantool
longevity testing
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.7k
- Forks
- 419
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 88
Description
Most part of our tests are functional and its duration is not more than 1-3 minutes on a single tarantool instance. So we are lack of load testing on a single tarantool for a long time, for example week, although it is usual practice to test server applications under a production (or production-like) load for a week.
This task is about:
- find load pattern and data for such test. Right now I see some variants. First one: take a real production Lua application, run it in a house and load it by requests. Second one: replay logs from production servers previously sanitize to avoid leaks. Second approach used in PostgreSQL testing: see Statement Playback, pgreplay-go, pgreplay
- add test to development cycle
Contributor guide
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 defining a production-like load pattern and dataset for a single Tarantool instance. Compare running a real Lua application with replaying sanitized production logs, using the PostgreSQL Statement Playback, pgreplay-go, and pgreplay references as context. The work is done when a long-running load test and its integration into the development cycle are specified and added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- databases, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100