Time/Place

Time: 3:00pm Eastern Standard Time US (UTC-5)
Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php

Attendees

Agenda

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)

JMeter Test Implementation

Other actions is to put together the quite simplest JMeter tests

(Just creating default containers)

(More about the mechanics about dealing with JMeter)

Some attendees of the calls have expressed some interest in the past

Thus far, haven't heard from anyone regarding implementation

Utility within the Ongoing Development of Fedora

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

A service (Blazemeter) can be hired (by DuraSpace) for JMeter test plans (executed in scale using, Amazon Web Services)

Progressing with JMeter

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

Are there other activities which can be addressed before the tests are implemented?

General sense is that this is a stopping point

Create a team in order to implement the first test?

Nick leads

James volunteers

Hardware...A. Wagner is on vacation until 01/04/16

Used for building different boxes

Is Wagner joining the team? Until the year, their time is limited

Nick

Moving forward...can spend next 1-2 days addressing this test

Push to repo, share it...

A. Woods has worked at it to some degree, all within the UI

James is more of a novice

Various test cases with different clients

Incremental effort, where the initial creation of containers...building on itself for the container creation, and then look at the other tests

72 hours of Nick's dedicated time

Will all be tagged on Confluence, Nick will comment and update on the status

Indicate any obstacles by Wednesday afternoon

Avoid forking the GitHub repository; Include the JMX file alone into a new repository

Ideally, make substantial progress before February 2016

Get a sense of how much effort it shall consume, produce a better estimate

No strong commitments this far...

Nice on the next call to have a better sense of when this initial set of tests shall be scripted out

Propose a meeting be scheduled into early 2016

A. Woods shall be unavailable throughout the early year (no access to WWW)

Hopefully have that meeting before A. Woods returns

01/11/15 11:00AM (EST)

Nick leads the time

(A. Wagner authors an agenda Page)

Agenda will be filled in with updates

Outreach

Reaching out to other groups...U. Michigan? Hydra-in-a-Box at Stanford U.?

It would be ideal to bring in other groups (beyond the core Fedora committers)

Page tree

2015-12-21 Performance - Scale Meeting