[
http://mifosforge.jira.com/browse/MIFOS-4581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64400#action_64400
]
Sumit Shah commented on MIFOS-4581:
-----------------------------------
The reason for the 5 different configurations:
1) a) corresponds to our current setup which allows for simple "multi tenancy"
apache layer routes different vhosts to different tomcat instances, so doing
(a) would establish a baseline and would provide a sanity check by allowing us
to compare existing performance numbers
2) b) required so we can get an idea of changing only to jetty while other
parameters remain constant
3) c) d) e) give us a better idea of performance in our new cloud system where
we do not front with apache.
if you want to reduce the number of permutations than taking (d) out is ok and
(b) maybe ok to remove too.
> 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: jbrewster
> Assignee: Chetan Bekkinkeri
>
> 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 contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
