[
http://mifosforge.jira.com/browse/MIFOS-4581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Łukasz Babski closed MIFOS-4581.
--------------------------------
I've checked attached results and conclusion is that Jetty has better results
in performance tests than Tomcat, so ticket can be closed. I am closing this
issue also because of performance test termination.
> Performance test comparisons - Tomcat and Jetty
> ------------------------------------------------
>
> Key: MIFOS-4581
> URL: http://mifosforge.jira.com/browse/MIFOS-4581
> Project: mifos
> Issue Type: Task
> Components: Performance
> Reporter: Jeff Brewster
> Assignee: Chetan Bekkinkeri
> Labels: sungard
> Attachments: env_Jetty.txt, EnvVariables_Tomcat_APR.txt, Jetty
> Documentation.docx, jetty.xml, OnlyJetty.rar, TomcatApacheAJP.rar,
> Tomcat-APRConnector.rar, TomcatAPRserver.xml, TomcatAPRweb.xml
>
>
> Background: We are considering replacing Tomcat with Jetty, see MIFOS-4099
> and http://tinyurl.com/4cy48qh.
> As part of that process, we need to be confident that our application will
> execute and perform at the same response time level (or better) than our
> current Tomcat deployment.
> Task includes:
> 1) setting up a test instance with Jetty 7.2.2.
> 2) run basic manual tests with deployed Mifos. Requires learning how to
> deploy Mifos with Jetty -
> http://docs.codehaus.org/display/JETTY/Newbie+Guide+to+Jetty.
> 3) Run current Jmeter performance tests for various configurations. Don't
> have to be run continuously. Can be run once and have results
> captured/documented. However, environments should be stored so tests can re
> rerun easily:
> a) tomcat with apache in front (over ajp) <- currently what is configured
> for existing cloud instances
> b) jetty with apache in front (over ajp)
> c) jetty with no apache
> d) tomcat with no apache (pure java connector)
> e) tomcat with no apache (apr connector) <- currently planned for new cloud
> instances
> Results of task:
> 1) ec2 image(s) that can used for this testing going forward if switch to
> jetty takes place.
> 2) report of measured results sent to project team.
> 3) any bugs or anomalies reported
> 4) basic documentation on using Mifos with jetty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
