Commit graph

9 commits

Author SHA1 Message Date
Yorick Peterse
89c65a3789 Increase Unicorn memory limits to 300-350
Using this limit on GitLab.com it appears we're able to reduce response
timings by about 620 milliseconds compared to the previous limit.

See gitlab-org/gitlab-ce!2421 for more information.
2016-01-20 11:52:01 +01:00
Yorick Peterse
21fab4f413 Use env variables for Unicorn memory limits
This makes it easier for users to use their own limits based on their
server configuration.
2016-01-20 11:51:49 +01:00
Robert Speicher
694743170c Disable Unicorn::WorkerKiller in non-production environments 2015-05-27 22:57:49 -04:00
Дамјан Георгиевски
be150fa991 Check specifically for Unicorn in rack config.ru file
Don't assume that if the Rack server is not Passenger then it must be Unicorn. There are many other Rack servers in the world (uwsgi being one example that people use a lot).

The reverse check is much more logical, i.e. check explicitly for Unicorn
2014-01-23 18:24:31 +01:00
dprolife
6b2ee67269 Fix 'uninitialized constant Unicorn' error 2013-12-22 11:08:43 +01:00
James Newton
756258ab1d don't use unicorn worker killer if PhusionPassenger is defined 2013-12-20 10:30:34 -06:00
Jacob Vosmaer
d27224ceca Add unicorn-worker-killer with memory check
Conflicts:
	Gemfile.lock
2013-12-18 16:52:14 +01:00
Chris Frohoff
21e55ca318 added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00:00
gitlabhq
9ba1224867 init commit 2011-10-09 00:36:38 +03:00