Backup needs "unreasonable" amounts of memory
Created by: tomplast
When I upgraded to 6.8 (used 6.6.before and don't know if 6.7 had the same problem) I suddenly started to get memory errors with unicorn every night when I run the backup task.
ERROR -- : Cannot allocate memory - fork(2) (Errno::ENOMEM)
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:496:in fork' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:496:inspawn_missing_workers'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:511:in maintain_worker_count' /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:277:injoin'
/home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.3/bin/unicorn_rails:209:in `<top (required)>'
After this I added more memory to the virtual machine that runs GitLab, from around 6Gb to around 14Gb. The errors has stopped but the memory usage is kept around 1,5Gb for the whole machine during the day and rises to about 9Gb when the backup is running!
I can understand that it needs some more memory during the backup but 6 times as much as the daily usage seems a little high I think.
The total size of my backups lies around 1Gb so it's not an enormous amount of data I think.
So is this high memory usage a bug or what?