The [fast SSH key lookup](../operations/fast_ssh_key_lookup.md) feature can improve
The [fast SSH key lookup](operations/fast_ssh_key_lookup.md) feature can improve
performance of GitLab instances even if they're using block storage.
performance of GitLab instances even if they're using block storage.
[Fast SSH key lookup](../operations/fast_ssh_key_lookup.md) is a replacement for
[Fast SSH key lookup](operations/fast_ssh_key_lookup.md) is a replacement for
`authorized_keys` (in `/var/opt/gitlab/.ssh`) using the GitLab database.
`authorized_keys` (in `/var/opt/gitlab/.ssh`) using the GitLab database.
NFS increases latency, so fast lookup is recommended if `/var/opt/gitlab`
NFS increases latency, so fast lookup is recommended if `/var/opt/gitlab`
...
@@ -147,7 +147,7 @@ From GitLab 12.7, Rugged auto-detection is disabled if Puma thread count is grea
...
@@ -147,7 +147,7 @@ From GitLab 12.7, Rugged auto-detection is disabled if Puma thread count is grea
If you want to use Rugged with Puma, it is recommended to [set Puma thread count to 1](https://docs.gitlab.com/omnibus/settings/puma.html#puma-settings).
If you want to use Rugged with Puma, it is recommended to [set Puma thread count to 1](https://docs.gitlab.com/omnibus/settings/puma.html#puma-settings).
If you want to use Rugged with Puma thread count more than 1, Rugged can be enabled using the [feature flag](../../development/gitaly.md#legacy-rugged-code)
If you want to use Rugged with Puma thread count more than 1, Rugged can be enabled using the [feature flag](../development/gitaly.md#legacy-rugged-code)
If the Rugged feature flag is explicitly set to either true or false, GitLab will use the value explicitly set.
If the Rugged feature flag is explicitly set to either true or false, GitLab will use the value explicitly set.
...
@@ -269,7 +269,7 @@ NFS mount point is `/gitlab-nfs`. Then, add the following bind mounts in
...
@@ -269,7 +269,7 @@ NFS mount point is `/gitlab-nfs`. Then, add the following bind mounts in
Using bind mounts will require manually making sure the data directories
Using bind mounts will require manually making sure the data directories
are empty before attempting a restore. Read more about the
are empty before attempting a restore. Read more about the
| NFS ([5](#footnotes)) ([7](#footnotes)) | Shared disk storage service. Can be used as an alternative Object Storage. Required for GitLab Pages | [NFS configuration](../high_availability/nfs.md) | No |
| NFS ([5](#footnotes)) ([7](#footnotes)) | Shared disk storage service. Can be used as an alternative Object Storage. Required for GitLab Pages | [NFS configuration](../high_availability/nfs.md) | No |
| [Consul](../../development/architecture.md#consul)([3](#footnotes)) | Service discovery and health checks/failover | [Consul configuration](../high_availability/consul.md)**(PREMIUM ONLY)** | Yes |
| [Consul](../../development/architecture.md#consul)([3](#footnotes)) | Service discovery and health checks/failover | [Consul configuration](../high_availability/consul.md)**(PREMIUM ONLY)** | Yes |
| Repmgr | PostgreSQL cluster management and failover | [PostgreSQL and Repmgr configuration](../postgresql/replication_and_failover.md) | Yes |
| Repmgr | PostgreSQL cluster management and failover | [PostgreSQL and Repmgr configuration](../postgresql/replication_and_failover.md) | Yes |
| Patroni | An alternative PostgreSQL cluster management and failover | [PostgreSQL and Patroni configuration](../postgresql/replication_and_failover.md#patroni) | Yes |
| Patroni | An alternative PostgreSQL cluster management and failover | [PostgreSQL and Patroni configuration](../postgresql/replication_and_failover.md#patroni) | Yes |
| [Redis](../../development/architecture.md#redis)([3](#footnotes)) | Key/value store for fast data lookup and caching | [Redis configuration](../high_availability/redis.md) | Yes |
| [Redis](../../development/architecture.md#redis)([3](#footnotes)) | Key/value store for fast data lookup and caching | [Redis configuration](../high_availability/redis.md) | Yes |