Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

performance: possible degradation after a lot of releases #105

Open
Totktonada opened this issue Dec 4, 2019 · 3 comments
Open

performance: possible degradation after a lot of releases #105

Totktonada opened this issue Dec 4, 2019 · 3 comments

Comments

@Totktonada
Copy link
Member

@andrew-statsenko proposed to verify the following case against possible performance degradation.

  1. 1000 puts;
  2. 100 take+ack;
  3. 900 take+release;
  4. Repeat from 1.
@LeonidVas LeonidVas self-assigned this Dec 11, 2019
@Totktonada
Copy link
Member Author

@LeonidVas AFAIR, you tried to reproduce it, but without lack. Can you share your approach (maybe scripts, workload sizes) and results?

@LeonidVas
Copy link
Contributor

From @andrew-statsenko:

...наш кейс:

— в очередь (стоковый tarantool/queue, master) с постоянной скоростью ставятся (put) новые задачи с примерной скоростью 300-500 rps в зависимости от текущей нагрузки.
— обработчики очереди, go client, 1024 goroutines, поднимают (take) задачи, их обрабатываются и делают им ack.

В силу некоторых ограничений дальнейшей цепи обработки поставленных задач мы не процессим более 10 rps от одного пользователя и при превышении этого лимита задачи возвращаются обратно в очередь (release with delay). Периодически случаются ситуации, когда очередь «забивается» задачами от одного пользователя и доля задач, которым обработчик делает relase with delay может достигать 50-70-90% на очередь. В это время наблюдается сильная деградация скорости обработки очереди — скорость take’а задач падает более, чем на порядок.

@LeonidVas
Copy link
Contributor

@LeonidVas AFAIR, you tried to reproduce it, but without lack. Can you share your approach (maybe scripts, workload sizes) and results?

I don't tried to reproduce it.

LeonidVas added a commit that referenced this issue Nov 25, 2020
LeonidVas added a commit that referenced this issue Nov 30, 2020
LeonidVas added a commit that referenced this issue Nov 30, 2020
@LeonidVas LeonidVas added the backlog Issues for upcoming releases (to be done soon) label Dec 15, 2020
LeonidVas added a commit that referenced this issue Dec 16, 2020
LeonidVas added a commit that referenced this issue Dec 16, 2020
LeonidVas added a commit that referenced this issue Dec 17, 2020
LeonidVas added a commit that referenced this issue Dec 22, 2020
LeonidVas added a commit that referenced this issue Dec 22, 2020
LeonidVas added a commit that referenced this issue Dec 24, 2020
@LeonidVas LeonidVas removed backlog Issues for upcoming releases (to be done soon) prio5 labels Jan 20, 2022
@LeonidVas LeonidVas removed their assignment Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants