...
- We have consensus on the test plans
- Next step: execute via JMeter (early Fedora example)
- ...
Minutes
- Consensus on test plans
(Achieved consensus, 5 people have liked the Page)
- Other actions is to put together the quite simplest JMeter tests
(Just creating default containers)
(More about the mechanics about dealing with JMeter)
Terry Reese not available
Haven't heard from anyone else
Some changes going on with the underlying Fedora implementation stack
Modeshape is undergoing a major release next year
Discussion of an alternate implementation
- Prove out the API
Baseline of tests now would be beneficial
Service can be hired (by DuraSpace) for JMeter test plans (executed in scale using Amazon) (Blazemeter)
Question: Given the test plans...what are the appropriate next steps?
Examples from JMeter tests a few years ago
Is it a matter of updating these configuration files?
XML or GUI for creating the test plans
A. Woods agrees with such an approach for creating...such an API
A. Wagner: New to Fedora...have used it on numerous occasions
Parties responsible for the JMeter? James proposing attempting to contact them
A. Woods has some pessimism
Look through commits...Nigel Banks and Chris Beer...Adam Soroka
Not much a learning curve with JMeter...more a matter of time
Limiting factor is time more than anything else
30 minutes to try to open up the JMeter UI, load JMX file, have enough skill at create the tests
Looking to implement test #4
If it gets too slow to be useful, the test is done
Not much more complexity than this
Ultimately, get to having JMeters for all 6 cases within the plan
Then, decide what to do with the information
Esme has been undertaking some testing
Baseline of information drives the components of Fedora which must be adjusted in order to improve performance
JVM configuration is included within the system profile