diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 09:07:59 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 09:07:59 +0000 |
commit | a325f3a104748ecc68df7c3d793940aa709a111f (patch) | |
tree | b3bce12be64ab2d9e31627dacd059165819797a3 /doc/development/performance.md | |
parent | 8fb943c7df5f2b399caaeaebd6c00d0630bc763c (diff) | |
download | gitlab-ce-a325f3a104748ecc68df7c3d793940aa709a111f.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/performance.md')
-rw-r--r-- | doc/development/performance.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/development/performance.md b/doc/development/performance.md index 1b3c4aedf1f..5697f41c3dc 100644 --- a/doc/development/performance.md +++ b/doc/development/performance.md @@ -259,10 +259,10 @@ One of the reasons of the increased memory footprint could be Ruby memory fragme To diagnose it, you can visualize Ruby heap as described in [this post by Aaron Patterson](https://tenderlovemaking.com/2017/09/27/visualizing-your-ruby-heap.html). -To start, you want to dump the heap of the process you're investigating to a JSON file. +To start, you want to dump the heap of the process you're investigating to a JSON file. -You need to run the command inside the process you're exploring, you may do that with `rbtrace`. -`rbtrace` is already present in GitLab `Gemfile`, you just need to require it. +You need to run the command inside the process you're exploring, you may do that with `rbtrace`. +`rbtrace` is already present in GitLab `Gemfile`, you just need to require it. It could be achieved running webserver or Sidekiq with the environment variable set to `ENABLE_RBTRACE=1`. To get the heap dump: @@ -281,7 +281,7 @@ Fragmented Ruby heap snapshot could look like this: ![Ruby heap fragmentation](img/memory_ruby_heap_fragmentation.png) -Memory fragmentation could be reduced by tuning GC parameters as described in [this post by Nate Berkopec](https://www.speedshop.co/2017/12/04/malloc-doubles-ruby-memory.html), which should be considered as a tradeoff, as it may affect overall performance of memory allocation and GC cycles. +Memory fragmentation could be reduced by tuning GC parameters as described in [this post by Nate Berkopec](https://www.speedshop.co/2017/12/04/malloc-doubles-ruby-memory.html). This should be considered as a tradeoff, as it may affect overall performance of memory allocation and GC cycles. ## Importance of Changes |