diff options
Diffstat (limited to 'doc/administration/instance_limits.md')
| -rw-r--r-- | doc/administration/instance_limits.md | 74 |
1 files changed, 57 insertions, 17 deletions
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md index ec56a59fdc2..0eede5f3ca5 100644 --- a/doc/administration/instance_limits.md +++ b/doc/administration/instance_limits.md @@ -1,7 +1,7 @@ --- -stage: none -group: unassigned -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers +stage: Enablement +group: Distribution +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: reference --- @@ -165,7 +165,7 @@ There is a limit when embedding metrics in GFM for performance reasons. On GitLab.com, the [maximum number of webhooks and their size](../user/gitlab_com/index.md#webhooks) per project, and per group, is limited. -To set this limit on a self-managed installation, run the following in the +To set this limit on a self-managed installation, where the default is `100` project webhooks and `50` group webhooks, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): ```ruby @@ -173,7 +173,7 @@ To set this limit on a self-managed installation, run the following in the # Plan.default.create_limits! # For project webhooks -Plan.default.actual_limits.update!(project_hooks: 100) +Plan.default.actual_limits.update!(project_hooks: 200) # For group webhooks Plan.default.actual_limits.update!(group_hooks: 100) @@ -181,6 +181,23 @@ Plan.default.actual_limits.update!(group_hooks: 100) Set the limit to `0` to disable it. +## Pull Mirroring Interval + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/237891) in GitLab 13.7. + +The [minimum time between pull refreshes](../user/project/repository/repository_mirroring.md) +defaults to 300 seconds (5 minutes). + +To change this limit on a self-managed installation, run the following in the +[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): + +```ruby +# If limits don't exist for the default plan, you can create one with: +# Plan.default.create_limits! + +Plan.default.actual_limits.update!(pull_mirror_interval_seconds: 200) +``` + ## Incoming emails from auto-responders > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/30327) in GitLab 12.4. @@ -235,8 +252,8 @@ If a new pipeline would cause the total number of jobs to exceed the limit, the will fail with a `job_activity_limit_exceeded` error. - On GitLab.com different [limits are defined per plan](../user/gitlab_com/index.md#gitlab-cicd) and they affect all projects under that plan. -- On [GitLab Starter](https://about.gitlab.com/pricing/#self-managed) tier or higher self-managed installations, this limit is defined for the `default` plan that affects all projects. - This limit is disabled by default. +- On [GitLab Starter](https://about.gitlab.com/pricing/#self-managed) tier or higher self-managed installations, this limit is defined under a `default` plan that affects all projects. + This limit is disabled (`0`) by default. To set this limit on a self-managed installation, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): @@ -250,6 +267,29 @@ Plan.default.actual_limits.update!(ci_active_jobs: 500) Set the limit to `0` to disable it. +### Maximum number of deployment jobs in a pipeline + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46931) in GitLab 13.7. + +You can limit the maximum number of deployment jobs in a pipeline. A deployment is +any job with an [`environment`](../ci/environments/index.md) specified. The number +of deployments in a pipeline is checked at pipeline creation. Pipelines that have +too many deployments fail with a `deployments_limit_exceeded` error. + +The default limit is 500 for all [self-managed and GitLab.com plans](https://about.gitlab.com/pricing/). + +To change the limit on a self-managed installation, change the `default` plan's limit with the following +[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session) command: + +```ruby +# If limits don't exist for the default plan, you can create one with: +# Plan.default.create_limits! + +Plan.default.actual_limits.update!(ci_pipeline_deployments: 500) +``` + +Set the limit to `0` to disable it. + ### Number of CI/CD subscriptions to a project > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9045) in GitLab 12.9. @@ -261,7 +301,7 @@ If a new subscription would cause the total number of subscription to exceed the limit, the subscription will be considered invalid. - On GitLab.com different [limits are defined per plan](../user/gitlab_com/index.md#gitlab-cicd) and they affect all projects under that plan. -- On [GitLab Starter](https://about.gitlab.com/pricing/#self-managed) tier or higher self-managed installations, this limit is defined for the `default` plan that affects all projects. +- On [GitLab Starter](https://about.gitlab.com/pricing/#self-managed) tier or higher self-managed installations, this limit is defined under a `default` plan that affects all projects. By default, there is a limit of `2` subscriptions. To set this limit on a self-managed installation, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): @@ -285,8 +325,8 @@ On GitLab.com, different limits are [defined per plan](../user/gitlab_com/index. and they affect all projects under that plan. On self-managed instances ([GitLab Starter](https://about.gitlab.com/pricing/#self-managed) -or higher tiers), this limit is defined for the `default` plan that affects all -projects. By default, there is no limit. +or higher tiers), this limit is defined under a `default` plan that affects all +projects. By default, there is a limit of `10` pipeline schedules. To set this limit on a self-managed installation, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): @@ -459,8 +499,8 @@ as the overall index size. This value defaults to `1024 KiB` (1 MiB) as any text files larger than this likely aren't meant to be read by humans. You must set a limit, as unlimited file sizes aren't supported. Setting this -value to be greater than the amount of memory on GitLab's Sidekiq nodes causes -GitLab's Sidekiq nodes to run out of memory, as they will pre-allocate this +value to be greater than the amount of memory on GitLab Sidekiq nodes causes +the GitLab Sidekiq nodes to run out of memory, as they will pre-allocate this amount of memory during indexing. ### Maximum field length @@ -527,12 +567,12 @@ More information can be found in the [Push event activities limit and bulk push On GitLab.com, the maximum file size for a package that's uploaded to the [GitLab Package Registry](../user/packages/package_registry/index.md) varies by format: -- Conan: 3GB +- Conan: 5GB - Generic: 5GB -- Maven: 3GB -- NPM: 500MB -- NuGet: 500MB -- PyPI: 3GB +- Maven: 5GB +- NPM: 5GB +- NuGet: 5GB +- PyPI: 5GB To set this limit on a self-managed installation, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): |