Hide Forgot
Description of problem: Many users that use this quickstart reporting performance issues on Online. This bug is about improving this cartridge to be 'usable' without performance penalty. Version-Release number of selected component (if applicable): openshift.com as of Dec 16, 2013 How reproducible: Always Steps to Reproduce: 1. Create a non-scaling Redmine app 2. 3. Actual results: Poor performance of the Redmine app from the user perspective Expected results: App performance should be faster Additional info:
After further investigation I found out that the problem was not in the performance of the quickstart it self but in the way how it was used. The point of the failure was that the user was using redmine quickstart on one small gear (not scalable), which didnt have enought resources to serve ruby cartrigde (RoR itself takes a lot of those resources) and MySQL cartridge. If the created app was scalable users wouldn't have this issue. The problem is that now the redmine quickstatrt doesnt support scaling. Will create an Trello cart on this, cause I think it is the right way how to improve the Redmine cartridge for speed.
Created attachment 838478 [details] Screenshot Screenshot, sent by one customer, showing how slow the quickstart is.
Fixed by PR : https://github.com/openshift/redmine-2.0-openshift-quickstart/pull/6 After advising them to use it as a scaled application, I found out that there is a problem that ruby cartridge can not connect to mysql cartridge which is on different gear. Problem fixed by adding the port number when connecting to the mysql or testing its presence.
Verified in INT(devenv_4223).Redmine quickstart works well.