Changes between Initial Version and Version 1 of JMeterModule


Ignore:
Timestamp:
09/13/12 23:59:51 (12 years ago)
Author:
jesseeichar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JMeterModule

    v1 v1  
     1= Improved security =
     2
     3|| '''Date''' || 2012/09/14 ||
     4|| '''Contact(s)''' || [http://wiki.osgeo.org/wiki/User:Jeichar Jesse Eichar] ||
     5|| '''Last edited''' || ||
     6|| '''Status''' || In Development ||
     7|| '''Assigned to release''' || 2.9.x ||
     8|| '''Resources''' || Funding Swisstopo ||
     9|| '''Code''' || https://github.com/jesseeichar/core-geonetwork/commits/feature/jmeter ||
     10
     11== Overview ==
     12
     13Add a jmeter module that, when requested, will run various performance tests against a geonetwork instance and provide a report of the results.
     14
     15=== Proposal Type ===
     16 * '''Type''': Security
     17 * '''App''': !GeoNetwork
     18 * '''Module''':
     19
     20=== Links ===
     21 
     22 * '''Email discussions''':
     23 * '''IRC discussions''':
     24 * '''Related work''':
     25  * http://jmeter.apache.org/
     26  * http://mojo.codehaus.org/chronos
     27
     28 
     29=== Voting History ===
     30
     31 * None as yet
     32
     33----
     34
     35
     36== Proposal ==
     37
     38In order to more easily track and detect performance problems a jmeter module will be created which will have a some jmeter tests defined and can be very easily ran and reports viewed.  The details are as follows:
     39
     40In project add a new jmeter maven module with the [chronos|http://mojo.codehaus.org/chronos] plugin for running jmeter tests and creating reports.  The default behaviour will be to use jetty to run Geonetwork and then run the jmeter tests against that instance.  The tests can be ran either standalone (just from the jmeter directory) or as part of a full build.  The history is tracked an therefore be used to track performance metrics overtime.
     41
     42In additional to being able to being ran against a Geonetwork ran in an embedded Jetty instance, it is possible to run the tests against an arbitrary Geonetwork instances by passing certain properties to the maven command.  See Properties below.
     43
     44
     45== Commands ==
     46
     47|| Command || Directory || Description ||
     48|| mvn install || jmeter || Start Geonetwork in embedded jetty and run jmeter tests against instance ||
     49|| mvn site:run || jmeter || Run the maven site jetty on port 9000.  The performance reports are under the Reports section ||
     50|| mvn install -P performance || root directory || Build geonetwork and run jmeter tests ||
     51|| mvn install -P -jmeter-jetty install || jmeter || Run jmeter tests but do not start embedded jetty ||
     52|| mvn install -P -jmeter-jetty -Dtestserver.host=otherserver.com -Dtestserver.port=80 install || jmeter || Run jmeter tests (no jetty) against http://otherserver.com:80/geonetwork||
     53
     54== Properties ==
     55
     56|| Property || Default || Description ||
     57|| testserver.host || localhost || the server to test ||
     58|| testserver.port || 9234 || the port to use in http requests ||
     59|| testserver.protocol || http || the protocol to use when making requests ||
     60|| admin.username || admin || the user name to use for loading sample data and editing metadata ||
     61|| admin.password || admin || the password for admin.username ||
     62|| base.url || /geonetwork || the base url to use when making requests.
     63If changed  base.loc.url will also have to be changed ||
     64|| base.loc.url || /geonetwork/srv/eng || the base url to use when making service requests ||
     65
     66=== Backwards Compatibility Issues ===
     67
     68No issues
     69
     70== Risks ==
     71
     72
     73== Participants ==
     74 * As above