Feature discussion: Redmine on OpenShift

Mo Morsi mmorsi at redhat.com
Wed Mar 28 13:47:01 UTC 2012


On 03/28/2012 09:34 AM, Matt Wagner wrote:
> On Wed, Mar 28, 2012 at 02:44:30PM +0200, Jan Provaznik wrote:
>> On 03/27/2012 10:26 PM, Matt Wagner wrote:
>>> Howdy teammates,
>>>
>>> One of the features to consider during our planning sprint was #3106,
>>> investigating moving our Redmine install to OpenShift, Red Hat's PaaS
>>> offering. The Express tier is free, and would free us from having to
>>> maintain the dedicated VM we run right now for Redmine. The real
>>> motivation for this task is that Redmine is sometimes _excruciatingly_
>>> slow, with responses sometimes exceeding ~35 seconds, at which point
>>> Apache times out the connection.
>>>
>> Hi Matt,
>> do you (or someone else) know what causes this delay? Is it just
>> because insufficient HW resources or some deployment settings?
> It looks like the Redmine machine is periodically running out of memory
> and making substantial use of swap. It has a gig of RAM is and using
> ~400MB of swap. I didn't dig too deeply into this. (Frankly, although
> 1GB is minuscule by modern standards and Rails isn't known as a
> lightweight framework, it's really surprising that a box really doing
> nothing but running thin needs more than that.)
>
>> I've no objections to OpenShift (honestly getting rid of maintaining
>> a machine is big plus) but if real motivation to switch is
>> performance problem I wonder if it can't be solved on the current
>> machine.
> If we could bump the machine up to 2GB of RAM, it would probably solve
> the slowness problem with some room to spare. But as you mention, part
> of the appeal of something like OpenShift is that, rather than chasing
> down performance problems on VMs (and trying to figure out who the
> person is to request a larger VM from), it's kind of appealing to just
> run it somewhere where we don't have to worry about any of this.
>
> -- Matt

Forwarded the request onto mburns to see if we can get more resources
dedicate to the vm.

/me would tend to try that and see if that works before moving to
openshift, the converse side of the "not having to worry about this"
argument is that we currently have full control over the environment
which our websites are running in and can easily expand / manipulate it
from there.

   -Mo




More information about the aeolus-devel mailing list