diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-24 03:08:46 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-24 03:08:46 +0300 |
commit | a85d15fdb3869157b467af20805f316d11739f74 (patch) | |
tree | 3778fb37e7e804d006e0fa19f9221fa1580ba833 /doc/administration/gitaly | |
parent | e79ee0307dfccb48871ee77ac3ebf6ae6a48117e (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/gitaly')
-rw-r--r-- | doc/administration/gitaly/configure_gitaly.md | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/doc/administration/gitaly/configure_gitaly.md b/doc/administration/gitaly/configure_gitaly.md index 47943820d44..ad7ecd1d796 100644 --- a/doc/administration/gitaly/configure_gitaly.md +++ b/doc/administration/gitaly/configure_gitaly.md @@ -872,10 +872,6 @@ When reached, limits _do_ result in disconnects that negatively impact users. For consistent and stable performance, you should first explore other options such as adjusting node specifications, and [reviewing large repositories](../../user/project/repository/managing_large_repositories.md) or workloads. -FLAG: -On self-managed GitLab, by default repository cgroups are not available. To make it available, an administrator can -[enable the feature flag](../feature_flags.md) named `gitaly_run_cmds_in_cgroup`. - When enabling cgroups for memory, you should ensure that no swap is configured on the Gitaly nodes as processes may switch to using that instead of being terminated. This situation could lead to notably compromised performance. |