# Performing Operations in GitLabKeep your GitLab instance up and running smoothly.-[Clean up Redis sessions](cleaning_up_redis_sessions.md): Prior to GitLab 7.3,user sessions did not automatically expire from Redis. Ifyou have been running a large GitLab server (thousands of users) since beforeGitLab 7.3 we recommend cleaning up stale sessions to compact the Redisdatabase after you upgrade to GitLab 7.3.-[Moving repositories](moving_repositories.md): Moving all repositories managedby GitLab to another file system or another server.-[Sidekiq MemoryKiller](sidekiq_memory_killer.md): Configure Sidekiq MemoryKillerto restart Sidekiq.
- Speed up SSH operations by [Authorizing SSH users via a fast,indexed lookup to the GitLab database](fast_ssh_key_lookup.md), and/orby [doing away with user SSH keys stored on GitLab entirely in favorof SSH certificates](ssh_certificates.md).
-[Filesystem Performance Benchmarking](filesystem_benchmarking.md): Filesystemperformance can have a big impact on GitLab performance, especially for actionsthat read or write Git repositories. This information will help benchmarkfilesystem performance against known good and bad real-world systems.