Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

Throttling BE tasks (under CPU stress) could be not enough. #89

Open
bwplotka opened this issue Sep 8, 2015 · 2 comments
Open

Throttling BE tasks (under CPU stress) could be not enough. #89

bwplotka opened this issue Sep 8, 2015 · 2 comments

Comments

@bwplotka
Copy link
Contributor

bwplotka commented Sep 8, 2015

Our throttled BE tasks can still interfere with LC PR task because they still can be scheduled for a short while by Linux Scheduler. They could create ctx switching and interfere with PR. (There could be no IPC drop, however interference appears)
Mitigations:

  • We should try to find a way to remove BE tasks when too many of them are on our node (even throttled)
  • Move BE jobs into Freezer cgroup?

We should make some experiments on how does BE task cntx switches affects LC task on different levels of PR utilization and amount of CPU-stress BE tasks.

@skonefal
Copy link
Contributor

skonefal commented Sep 8, 2015

Maybe, this could also be solved @ Mesos level.

Vinod has raised this issue on Community sync on Sept 3rd, 2015
https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit

@skonefal
Copy link
Contributor

skonefal commented Feb 1, 2016

Can we consider it done?
We have OverloadDetector in Serenity and load-based QoS Controller in Mesos.

If we would like to introduce cpu-pinning, we should do that in separate issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants