3 ms·
It appears that the workaround is open source, though, and is loaded in the open source version? https://github.com/gitlabhq/gitlabhq/blob/master/lib/gitlab/si
by btown 8y ago
It appears that the workaround is open source, though, and is loaded in the open source version?
https://github.com/gitlabhq/gitlabhq/blob/master/lib/gitlab/sidekiq_middleware/shutdown.rb https://github.com/gitlabhq/gitlabhq/blob/master/lib/gitlab/...
https://github.com/gitlabhq/gitlabhq/blob/master/config/initializers/sidekiq.rb#L15 https://github.com/gitlabhq/gitlabhq/blob/master/config/init...
Many other reasons to be concerned about performance, but there's no evidence that they're withholding essential features like this from their free version.
- swills 8y agoSorry, you're right, I misspoke. I should have said the CE version has the work around, but it's disabled by default.
- dblessing 8y agoThe Sidekiq memory killer is enabled for both CE and EE by default with the Omnibus package. If you're seeing something different please let us know and we'll see what's going on.