Scalability testing - Revision history

Courtney at 00:08, 17 October 2013

2013-10-17T00:08:04Z

Courtney at 15:35, 6 August 2013

2013-08-06T15:35:35Z

Courtney at 15:35, 6 August 2013

2013-08-06T15:35:21Z

Jhs at 18:01, 11 January 2013

2013-01-11T18:01:55Z

Jhs at 18:00, 11 January 2013

2013-01-11T18:00:11Z

Peter: /* Current Plans */

2013-01-11T17:54:28Z

Current Plans

Peter at 17:54, 11 January 2013

2013-01-11T17:54:03Z

Jhs at 17:39, 11 January 2013

2013-01-11T17:39:33Z

Jhs at 17:37, 11 January 2013

2013-01-11T17:37:28Z

Show changes

Jhs at 17:33, 11 January 2013

2013-01-11T17:33:06Z

← Older revision		Revision as of 00:08, 17 October 2013
Line 1:		Line 1:
−	[[Main Page~~]] > [[Development_roadmap:_Archivematica_1.0\|Development roadmap~~]] > Scalability testing	+	[[Main Page]] > Scalability testing

	= Objectives =		= Objectives =

← Older revision		Revision as of 15:35, 6 August 2013
Line 1:		Line 1:
−	[[Main Page]] > [[Development_roadmap:_Archivematica_1.0 Development roadmap]] > Scalability testing	+	[[Main Page]] > [[Development_roadmap:_Archivematica_1.0\|Development roadmap]] > Scalability testing

	= Objectives =		= Objectives =

← Older revision		Revision as of 15:35, 6 August 2013
Line 1:		Line 1:
−	[[Main Page]] > [[Development roadmap]] > Scalability testing	+	[[Main Page]] > [[Development_roadmap:_Archivematica_1.0 Development roadmap]] > Scalability testing

	= Objectives =		= Objectives =

← Older revision		Revision as of 18:01, 11 January 2013
Line 26:		Line 26:

	Scalability testing is done using a scripted workload, where all decision points, that are normally left to the Archivist to make using the Dashboard, are instead automated through the use of a configuration file. This allows for repeatable test cases. Example test scripts will be posted here over the coming weeks.		Scalability testing is done using a scripted workload, where all decision points, that are normally left to the Archivist to make using the Dashboard, are instead automated through the use of a configuration file. This allows for repeatable test cases. Example test scripts will be posted here over the coming weeks.
		+

	= Test File Sets =		= Test File Sets =

@@ Line 21: / Line 21: @@
 '''4. repeat test suite at customer sites'''
-<br>The two initial customer sites have been identified by Archivematica and tests will be repeasted at both customer sites.
+<br>The two initial customer sites have been identified by Archivematica and tests will be repeated at both customer sites.
 = Test Structure =

@@ Line 1: / Line 1: @@
 [[Main Page]] > [[Development roadmap]] > Scalability testing
-= Current Plans =
+= Objectives =
-'''* set up a dedicated testing environment'''
+'''1. set up a dedicated testing environment'''
 <br>
 The testing environment will start with 5 virtual machines set up in a hosted environment, where hardware resources can be scaled up and down between tests.  It is expected that the test environment will be ready to use by January 15th.
@@ Line 9: / Line 9: @@
-'''* develop a new initial repeatable test suite'''
+'''2. develop a new initial repeatable test suite'''
 <br>Initial tests will focus on two main areas - file io and documenting individual micro-service performance.  Data will be collected from external monitoring tools as well as from internal instrumentation.
@@ Line 15: / Line 15: @@
 Internal instrumentation already exists within the Archivematica source code, where each step in the process has a start time and end time recorded in the local database.  This instrumentation will be extended and refined during the buildout of the test suite.  The data collected will be used to identify which specific micro-services, and which steps within those micro-services are taking the longest time to complete.
-'''* document a full matrix of test parameters'''
+'''3. document a full matrix of test parameters'''
 <br>Archivematica workflow can vary considerably depending on use case.  Artefactual will document all testing efforts on this wiki, building out a matrix of test cases.  For example, we expect that adding additional storage subsystem capacity will allow for linear growth in scalability (add more disks, it should all go faster).  This will be one of the first 'columns' in our test matrix, repeating tests with the same workload, changing the capacity (maximum io's per second) of the storage subsystem between tests.
 Initial tests will focus on the 4 primary stages in the Archivematica workflow - Transfer, Ingest, creation of SIP, creation of AIP.  There are additional steps required, both before Transfer, and after creation of AIP, however these steps do not necessarily involve the use of Archivematica code.  For example, moving digital objects to a shared folder that Archivematica can access is a prerequisite of the Transfer stage, and can take a considerable amount of time.  We will document best practices for how to complete that work after initial scalability testing is complete.
-'''* repeat test suite at customer sites'''
+'''4. repeat test suite at customer sites'''
 <br>The two initial customer sites have been identified by Archivematica and tests will be repeasted at both customer sites.
 = Test Structure =

← Older revision		Revision as of 17:54, 11 January 2013
Line 2:		Line 2:

	= Current Plans =		= Current Plans =
−	~~January 11, 2013 - Artefactual is committing resources towards Scalability Testing for Archivematica over the coming weeks and months.~~
−
−	~~The main goals of this effort are:~~

	'''* set up a dedicated testing environment'''		'''* set up a dedicated testing environment'''

← Older revision		Revision as of 17:39, 11 January 2013
Line 9:		Line 9:
	<br>		<br>
	The testing environment will start with 5 virtual machines set up in a hosted environment, where hardware resources can be scaled up and down between tests. It is expected that the test environment will be ready to use by January 15th.		The testing environment will start with 5 virtual machines set up in a hosted environment, where hardware resources can be scaled up and down between tests. It is expected that the test environment will be ready to use by January 15th.
		+	[[Test Environment Documentation]]

@@ Line 5: / Line 5: @@
 The main goals of this effort are:
 '''
-* set up a dedicated testing environment'''<br>
+'''* set up a dedicated testing environment'''
 The testing environment will start with 5 virtual machines set up in a hosted environment, where hardware resources can be scaled up and down between tests.  It is expected that the test environment will be ready to use by January 15th.