- Impact Analysis
- Performance Review
- Think outside of the box
- Data set
- Query plans and database structure
- Query Counts
- Executing Queries in Loops
- Batch process
- Keep database transaction minimal
- Eager Loading
- Memory Usage
- Lazy Rendering of UI Elements
- Instrumenting New Code
- Use of Caching
- Badge counters
- Application/misuse limits
- Usage of feature flags
Each new introduced merge request should be performant by default.
To ensure a merge request does not negatively impact performance of GitLab every merge request should adhere to the guidelines outlined in this document. There are no exceptions to this rule unless specifically discussed with and agreed upon by backend maintainers and performance specialists.
To measure the impact of a merge request you can use Sherlock. It’s also highly recommended that you read the following guides:
SHOULD per the RFC 2119 means:
This word, or the adjective “RECOMMENDED”, mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
Ideally, each of these tradeoffs should be documented in the separate issues, labeled accordingly and linked to original issue and epic.
Summary: think about the impact your merge request may have on performance and those maintaining a GitLab setup.
Any change submitted can have an impact not only on the application itself but also those maintaining it and those keeping it up and running (for example, production engineers). As a result you should think carefully about the impact of your merge request on not only the application but also on the people keeping it up and running.
Can the queries used potentially take down any critical services and result in engineers being woken up in the night? Can a malicious user abuse the code to take down a GitLab instance? Will my changes simply make loading a certain page slower? Will execution time grow exponentially given enough load or data in the database?
These are all questions one should ask themselves before submitting a merge request. It may sometimes be difficult to assess the impact, in which case you should ask a performance specialist to review your code. See the “Reviewing” section below for more information.
Summary: ask performance specialists to review your code if you’re not sure about the impact.
Sometimes it’s hard to assess the impact of a merge request. In this case you should ask one of the merge request reviewers to review your changes. You can find a list of these reviewers at https://about.gitlab.com/company/team/. A reviewer in turn can request a performance specialist to review the changes.
Everyone has their own perception how the new feature is going to be used. Always consider how users might be using the feature instead. Usually, users test our features in a very unconventional way, like by brute forcing or abusing edge conditions that we have.
The data set that will be processed by the merge request should be known and documented. The feature should clearly document what the expected data set is for this feature to process, and what problems it might cause.
If you would think about the following example that puts a strong emphasis of data set being processed. The problem is simple: you want to filter a list of files from some Git repository. Your feature requests a list of all files from the repository and perform search for the set of files. As an author you should in context of that problem consider the following:
- What repositories are going to be supported?
- How long it will take for big repositories like Linux kernel?
- Is there something that we can do differently to not process such a big data set?
- Should we build some fail-safe mechanism to contain computational complexity? Usually it’s better to degrade the service for a single user instead of all users.
The query plan can tell us if we will need additional indexes, or expensive filtering (such as using sequential scans).
Each query plan should be run against substantial size of data set. For example, if you look for issues with specific conditions, you should consider validating a query against a small number (a few hundred) and a big number (100_000) of issues. See how the query will behave if the result will be a few and a few thousand.
This is needed as we have users using GitLab for very big projects and in a very unconventional way. Even if it seems that it’s unlikely that such a big data set will be used, it’s still plausible that one of our customers will encounter a problem with the feature.
Understanding ahead of time how it’s going to behave at scale, even if we accept it, is the desired outcome. We should always have a plan or understanding of what it will take to optimize the feature for higher usage patterns.
Every database structure should be optimized and sometimes even over-described in preparation for easy extension. The hardest part after some point is data migration. Migrating millions of rows will always be troublesome and can have a negative impact on the application.
To better understand how to get help with the query plan reviews read this section on how to prepare the merge request for a database review.
Summary: a merge request should not increase the number of executed SQL queries unless absolutely necessary.
The number of queries executed by the code modified or added by a merge request must not increase unless absolutely necessary. When building features it’s entirely possible you will need some extra queries, but you should try to keep this at a minimum.
As an example, say you introduce a feature that updates a number of database rows with the same value. It may be very tempting (and easy) to write this using the following pseudo code:
objects_to_update.each do |object| object.some_field = some_value object.save end
This will end up running one query for every object to update. This code can easily overload a database given enough rows to update or many instances of this code running in parallel. This particular problem is known as the “N+1 query problem”. You can write a test with QueryRecoder to detect this and prevent regressions.
In this particular case the workaround is fairly easy:
This uses ActiveRecord’s
update_all method to update all rows in a single
query. This in turn makes it much harder for this code to overload a database.
Summary: SQL queries must not be executed in a loop unless absolutely necessary.
Executing SQL queries in a loop can result in many queries being executed depending on the number of iterations in a loop. This may work fine for a development environment with little data, but in a production environment this can quickly spiral out of control.
There are some cases where this may be needed. If this is the case this should be clearly mentioned in the merge request description.
Summary: Iterating a single process to external services (for example, PostgreSQL, Redis, Object Storage) should be executed in a batch-style in order to reduce connection overheads.
For fetching rows from various tables in a batch-style, please see Eager Loading section.
When you delete multiple files from object storage, like GCS, executing a single REST API call multiple times is a quite expensive process. Ideally, this should be done in a batch-style, for example, S3 provides batch deletion API, so it’d be a good idea to consider such an approach.
FastDestroyAll module might help this situation. It’s a
small framework when you remove a bunch of database rows and its associated data
in a batch style.
Summary: You should set a reasonable timeout when the system invokes HTTP calls to external services (such as Kubernetes), and it should be executed in Sidekiq, not in Puma/Unicorn threads.
Often, GitLab needs to communicate with an external service such as Kubernetes clusters. In this case, it’s hard to estimate when the external service finishes the requested process, for example, if it’s a user-owned cluster that’s inactive for some reason, GitLab might wait for the response forever (Example). This could result in Puma/Unicorn timeout and should be avoided at all cost.
You should set a reasonable timeout, gracefully handle exceptions and surface the errors in UI or logging internally.
ReactiveCaching is one of the best solutions to fetch external data.
Summary: You should avoid accessing to external services like Gitaly during database transactions, otherwise it leads to severe contention problems as an open transaction basically blocks the release of a PostgreSQL backend connection.
For keeping transaction as minimal as possible, please consider using
after_commit AR hook.
Here is an example that one request to Gitaly instance during transaction triggered a P1 issue.
Summary: always eager load associations when retrieving more than one row.
When retrieving multiple database records for which you need to use any associations you must eager load these associations. For example, if you’re retrieving a list of blog posts and you want to display their authors you must eager load the author associations.
In other words, instead of this:
Post.all.each do |post| puts post.author.name end
You should use this:
Post.all.includes(:author).each do |post| puts post.author.name end
Also consider using QueryRecoder tests to prevent a regression when eager loading.
Summary: merge requests must not increase memory usage unless absolutely necessary.
A merge request must not increase the memory usage of GitLab by more than the absolute bare minimum required by the code. This means that if you have to parse some large document (for example, an HTML document) it’s best to parse it as a stream whenever possible, instead of loading the entire input into memory. Sometimes this isn’t possible, in that case this should be stated explicitly in the merge request.
Summary: only render UI elements when they are actually needed.
Certain UI elements may not always be needed. For example, when hovering over a diff line there’s a small icon displayed that can be used to create a new comment. Instead of always rendering these kind of elements they should only be rendered when actually needed. This ensures we don’t spend time generating Haml/HTML when it’s not going to be used.
Summary: always add instrumentation for new classes, modules, and methods.
Newly added classes, modules, and methods must be instrumented. This ensures we can track the performance of this code over time.
For more information see Instrumentation. This guide describes how to add instrumentation and where to add it.
Summary: cache data in memory or in Redis when it’s needed multiple times in a transaction or has to be kept around for a certain time period.
Sometimes certain bits of data have to be re-used in different places during a transaction. In these cases this data should be cached in memory to remove the need for running complex operations to fetch the data. You should use Redis if data should be cached for a certain time period instead of the duration of the transaction.
For example, say you process multiple snippets of text containing username
mentions (for example,
Hello @alice and
How are you doing @alice?). By caching the
user objects for every username we can remove the need for running the same
query for every mention of
Caching data per transaction can be done using
Gitlab::SafeRequestStore to avoid having to remember to check
RequestStore.active?). Caching data in Redis can be done using Rails’ caching
Each feature that renders a list of items as a table needs to include pagination.
The main styles of pagination are:
- Offset-based pagination: user goes to a specific page, like 1. User sees the next page number, and the total number of pages. This style is well supported by all components of GitLab.
- Offset-based pagination, but without the count: user goes to a specific page, like 1. User sees only the next page number, but does not see the total amount of pages.
- Next page using keyset-based pagination: user can only go to next page, as we don’t know how many pages are available.
- Infinite scrolling pagination: user scrolls the page and next items are loaded asynchronously. This is ideal, as it has exact same benefits as the previous one.
The ultimately scalable solution for pagination is to use Keyset-based pagination. However, we don’t have support for that at GitLab at that moment. You can follow the progress looking at API: Keyset Pagination .
Take into consideration the following when choosing a pagination strategy:
- It’s very inefficient to calculate amount of objects that pass the filtering, this operation usually can take seconds, and can time out,
- It’s very inefficient to get entries for page at higher ordinals, like 1000. The database has to sort and iterate all previous items, and this operation usually can result in substantial load put on database.
Counters should always be truncated. It means that we don’t want to present the exact number over some threshold. The reason for that is for the cases where we want to calculate exact number of items, we effectively need to filter each of them for the purpose of knowing the exact number of items matching.
From ~UX perspective it’s often acceptable to see that you have over 1000+ pipelines, instead of that you have 40000+ pipelines, but at a tradeoff of loading page for 2s longer.
An example of this pattern is the list of pipelines and jobs. We truncate numbers to
but we show an accurate number of running pipelines, which is the most interesting information.
There’s a helper method that can be used for that purpose -
that accepts an upper limit of counting rows.
In some cases it’s desired that badge counters are loaded asynchronously. This can speed up the initial page load and give a better user experience overall.
Every new feature should have safe usage quotas introduced. The quota should be optimised to a level that we consider the feature to be performant and usable for the user, but not limiting.
We want the features to be fully usable for the users. However, we want to ensure that the feature will continue to perform well if used at its limit and it won’t cause availability issues.
Consider that it’s always better to start with some kind of limitation, instead of later introducing a breaking change that would result in some workflows breaking.
The intent is to provide a safe usage pattern for the feature, as our implementation decisions are optimised for the given data set. Our feature limits should reflect the optimisations that we introduced.
The intent of quotas could be different:
- We want to provide higher quotas for higher tiers of features: we want to provide on GitLab.com more capabilities for different tiers,
- We want to prevent misuse of the feature: someone accidentally creates 10000 deploy tokens, because of a broken API script,
- We want to prevent abuse of the feature: someone purposely creates a 10000 pipelines to take advantage of the system.
Pipeline Schedules: It’s very unlikely that user will want to create more than 50 schedules. In such cases it’s rather expected that this is either misuse or abuse of the feature. Lack of the upper limit can result in service degradation as the system will try to process all schedules assigned the project.
GitLab CI/CD includes: We started with the limit of maximum of 50 nested includes. We understood that performance of the feature was acceptable at that level. We received a request from the community that the limit is too small. We had a time to understand the customer requirement, and implement an additional fail-safe mechanism (time-based one) to increase the limit 100, and if needed increase it further without negative impact on availability of the feature and GitLab.
Each feature that has performance critical elements or has a known performance deficiency needs to come with feature flag to disable it.
The feature flag makes our team more happy, because they can monitor the system and quickly react without our users noticing the problem.
Performance deficiencies should be addressed right away after we merge initial changes.
Read more about when and how feature flags should be used in Feature flags in GitLab development.
We can consider the following types of storages:
Local temporary storage (very-very short-term storage) This type of storage is system-provided storage, ex.
/tmpfolder. This is the type of storage that you should ideally use for all your temporary tasks. The fact that each node has its own temporary storage makes scaling significantly easier. This storage is also very often SSD-based, thus is significantly faster. The local storage can easily be configured for the application with the usage of
Shared temporary storage (short-term storage) This type of storage is network-based temporary storage, usually run with a common NFS server. As of Feb 2020, we still use this type of storage for most of our implementations. Even though this allows the above limit to be significantly larger, it does not really mean that you can use more. The shared temporary storage is shared by all nodes. Thus, the job that uses significant amount of that space or performs a lot of operations will create a contention on execution of all other jobs and request across the whole application, this can easily impact stability of the whole GitLab. Be respectful of that.
Shared persistent storage (long-term storage) This type of storage uses shared network-based storage (ex. NFS). This solution is mostly used by customers running small installations consisting of a few nodes. The files on shared storage are easily accessible, but any job that is uploading or downloading data can create a serious contention to all other jobs. This is also an approach by default used by Omnibus.
Object-based persistent storage (long term storage) this type of storage uses external services like AWS S3. The Object Storage can be treated as infinitely scalable and redundant. Accessing this storage usually requires downloading the file in order to manipulate it. The Object Storage can be considered as an ultimate solution, as by definition it can be assumed that it can handle unlimited concurrent uploads and downloads of files. This is also ultimate solution required to ensure that application can run in containerized deployments (Kubernetes) at ease.
The storage on production nodes is really sparse. The application should be built
in a way that accommodates running under very limited temporary storage.
You can expect the system on which your code runs has a total of
of temporary storage. However, this storage is really shared across all
jobs being run. If your job requires to use more than
100MB of that space
you should reconsider the approach you have taken.
Whatever your needs are, you should clearly document if you need to process files.
If you require more than
100MB, consider asking for help from a maintainer
to work with you to possibly discover a better solution.
The usage of local storage is a desired solution to use,
especially since we work on deploying applications to Kubernetes clusters.
When you would like to use
Dir.mktmpdir? In a case when you want for example
to extract/create archives, perform extensive manipulation of existing data, etc.
Dir.mktmpdir('designs') do |path| # do manipulation on path # the path will be removed once # we go out of the block end
The usage of shared temporary storage is required if your intent
is to persistent file for a disk-based storage, and not Object Storage.
Workhorse direct_upload when accepting file
can write it to shared storage, and later GitLab Rails can perform a move operation.
The move operation on the same destination is instantaneous.
The system instead of performing
copy operation just re-attaches file into a new place.
Since this introduces extra complexity into application, you should only try
to re-use well established patterns (ex.:
ObjectStorage concern) instead of re-implementing it.
The usage of shared temporary storage is otherwise deprecated for all other usages.
It is required that all features holding persistent files support saving data to Object Storage. Having a persistent storage in the form of shared volume across nodes is not scalable, as it creates a contention on data access all nodes.
GitLab offers the ObjectStorage concern that implements a seamless support for Shared and Object Storage-based persistent storage.
Each feature that accepts data uploads or allows to download them needs to use Workhorse direct_upload. It means that uploads needs to be saved directly to Object Storage by Workhorse, and all downloads needs to be served by Workhorse.
Performing uploads/downloads via Unicorn/Puma is an expensive operation, as it blocks the whole processing slot (worker or thread) for the duration of the upload.
Performing uploads/downloads via Unicorn/Puma also has a problem where the operation can time out, which is especially problematic for slow clients. If clients take a long time to upload/download the processing slot might be killed due to request processing timeout (usually between 30s-60s).
For the above reasons it is required that Workhorse direct_upload is implemented for all file uploads and downloads.