Astra Schedule Help (7.5)

Performance Benchmarking Data

Hide Navigation Pane

Performance Benchmarking Data

Previous topic Next topic  

Performance Benchmarking Data

Previous topic Next topic JavaScript is required for the print function  

Performance benchmarking statistics are provided here for comparison purposes.  Performance tests were performed by Ad Astra QA staff on Ad Astra hardware.  Find the sub-topic for the closest version to see statistics relevant to your installation.

 

Following are definitions for the standard performance test scenarios used by Ad Astra:

 

Scenario

Definition

Event Save

This is the time it took for the event to save after room assignment and resource assignment has been completed. This test scenario is executed multiple times with a variety of meeting instances.

Event Room Assignment

This is the time it took for the room assignment for all meeting instances of the event to be saved. This test scenario is executed multiple times with a variety of meeting instances.

Event Resource Assignment

This is the time it took for the resource assignment for a single meeting instance of the event to be saved. This test scenario is executed multiple times with a variety of meeting instances.

Event Save w/ Setup/Tear Down

This is the time it took for the event to save after room assignment, resource assignment, and setup/tear down window assignment. This test scenario is executed on a 50 meeting event.

Event Save w/ edits

This is the time it took for the event to save after room assignment and resource assignment has been completed and saved, but then the event is re-opened to re-assign a room, and then saved again. This test scenario is executed on a 50 meeting event.

Academic Edit: Room Assignment

This is the time it took to manually assign or reassign a room to a section with an average of 30 meeting instances via the Ad Hoc Scheduling tool. This test scenario included modifying the Ad Hoc Scheduling tool to display additional meeting patterns and non-standard meeting patterns with zero Contact Hours.

Academic Edit: Meeting Pattern

This is the time it took to manually modify the meeting pattern for a section with an average of 30 meeting instances. This test scenario included a change of the Start Time, Duration, and Days Met of the section.

Optimizer Run

This is the time it took to complete a sandbox optimization of a term of sections. The number of sections considered for optimization is noted.

Section Import

This is the time it took to complete an import of a term of sections from the SIS database. The number of sections imported in the term is noted.

Section Export

This is the time it took to complete an export of a single section's edit, (room reassignment, for example), back to the SIS database.