Performing operations in GitLab

Keep your GitLab instance up and running smoothly.

• Clean up Redis sessions: Prior to GitLab 7.3, user sessions did not automatically expire from Redis. If you have been running a large GitLab server (thousands of users) since before GitLab 7.3 we recommend cleaning up stale sessions to compact the Redis database after you upgrade to GitLab 7.3.
• Rake tasks: Tasks for common administration and operational processes such as cleaning up unneeded items from GitLab instance, integrity checks, and more.
• Moving repositories: Moving all repositories managed by GitLab to another file system or another server.
• Sidekiq MemoryKiller: Configure Sidekiq MemoryKiller to restart Sidekiq.
• Multiple Sidekiq processes: Configure multiple Sidekiq processes to ensure certain queues always have dedicated workers, no matter the number of jobs that need to be processed.
• Sidekiq routing rules: Configure the routing rules to route a job from a worker to a desirable queue.
• Puma: Understand Puma and puma-worker-killer.
• Speed up SSH operations by Authorizing SSH users via a fast, indexed lookup to the GitLab database, and/or by doing away with user SSH keys stored on GitLab entirely in favor of SSH certificates.
• File System Performance Benchmarking: File system performance can have a big impact on GitLab performance, especially for actions that read or write Git repositories. This information will help benchmark file system performance against known good and bad real-world systems.
• The Rails Console: Provides a way to interact with your GitLab instance from the command line. Used for troubleshooting a problem or retrieving some data that can only be done through direct access to GitLab.
• ChatOps Scripts: The GitLab.com Infrastructure team uses this repository to house common ChatOps scripts they use to troubleshoot and maintain the production instance of GitLab.com. These scripts are likely useful to administrators of GitLab instances of all sizes.