SDSM:Performance Measurements

This document consists of multiple parts; for a directory to all of the parts, see SDSM:Index.

Description

This part of the SDS Modernization (SDSM) document provides a list of SDS user interface screens and performance measurements for them as seen on its production instance (https://sds.smus.ca).

The list of screens is not exhaustive, and serves as a representative sample, in particular to provide visibility into historical progress of the SDS Modernization (SDSM) project with respect to how it improved the measured performance of SDS features over time.

See also the document part List of Screens that provides some context for this part.

This document part is organized first by access path for the screens, meaning by the path one takes through the main menus to reach them, and then for each screen, at least one or typically multiple performance measurements at different dates are given, organized earliest to latest.

Any given measurement should be considered to only be valid for the date on which it was measured, and not necessarily for any earlier or later date; but in practice, if it was measured again on the day this SDSM document was being read, it would likely be similar to the latest reported.

Every measurement is of the simple act of loading or refreshing a screen as a read-only action that doesn't try to add/edit/remove/etc data, unless otherwise explicitly stated.

Each measurement is within the context of a specific user, campus, and date, and sometimes other variables, since the app may behave differently and have different performance characteristics that depend on such, and comparisons over time or repeatable tests need to keep them consistent; most contextual variables only exist or apply for a user who is logged in.

These are the meanings of some context-defining terms:

• Measured on: The actual real world date the measurement was made.
• When as: The user that the app is is currently pretending is the current logged in user, via an impersonation, if it isn't the actual logged in user.
• Effective date: The date that the app is currently pretending is the current date, if it isn't the real world date.
• Effective campus: The campus that the app is currently pretending is where the logged in user is located.

If a measurement does not have an explicitly stated effective date, this should be read as if it were the same as measured on.

If a measurement does not have an explicitly stated effective campus, this should be read as if it were Senior School.

These are who the effective users are:

• DRD: Darren Duncan, who has a debug role, is effectively a staff member, is not a teacher or parent or student.
• RC: Richard Curry, who is both a teacher and a parent.
• CA: Carol Adamson, who is a teacher.

Typically each measurement is taken at least 3 times back to back and then the one with the shortest time is the one used.

RETURN

SDS Gavintech: Public Home

The SDS Gavintech: Public Home screen is where an app user typically starts when they first visit the app and have not yet authenticated or logged in to it.

https://sds.smus.ca

Measured on Thu 2024 Aug 29, when not logged in:

   Page generation time: 0.027
   Total SQL Queries: 4
   Total SQL Cache Hits: 1
   Total Local Cache Hits:
   Total Memcache Hits:
   Memory Usage: 2048K
   Realpath Usage: 229K

Measured on Wed 2024 Sep 4, when not logged in:

   Page generation time: 0.016
   Total SQL Queries: 4
   Total SQL Cache Hits: 1
   Total Local Cache Hits:
   Total Memcache Hits:
   Memory Usage: 2048K
   Realpath Usage: 322K

RETURN

SDS Gavintech: Private Home

The SDS Gavintech: Private Home screen is where an app user typically starts once they have authenticated or logged in to it.

https://sds.smus.ca

Measured on Thu 2024 Aug 29, when as DRD, effective date Thu, 2024 Aug 29:

   Page generation time: 0.519
   Total SQL Queries: 563
   Total SQL Cache Hits: 4026
   Total Local Cache Hits: 26
   Total Memcache Hits:
   Memory Usage: 14336K
   Realpath Usage: 277K

Measured on Wed 2024 Sep 4, when as DRD, effective date Thu, 2024 Aug 29:

   Page generation time: 0.157
   Total SQL Queries: 51
   Total SQL Cache Hits: 3536
   Total Local Cache Hits: 21
   Total Memcache Hits:
   Memory Usage: 4096K
   Realpath Usage: 335K

Measured on Thu 2024 Aug 29, when as DRD, effective date Mon 2024 Jun 3:

   Page generation time: 1.639
   Total SQL Queries: 1814
   Total SQL Cache Hits: 7220
   Total Local Cache Hits: 101
   Total Memcache Hits:
   Memory Usage: 36864K
   Realpath Usage: 190K

Measured on Wed 2024 Sep 4, when as DRD, effective date Mon 2024 Jun 3:

   Page generation time: 0.264
   Total SQL Queries: 205
   Total SQL Cache Hits: 3598
   Total Local Cache Hits: 59
   Total Memcache Hits:
   Memory Usage: 6144K
   Realpath Usage: 248K

Measured on Thu 2024 Aug 29, when as RC, effective date Mon 2024 Jun 3:

   Page generation time: 1.956
   Total SQL Queries: 1911
   Total SQL Cache Hits: 8673
   Total Local Cache Hits: 111
   Total Memcache Hits:
   Memory Usage: 38912K
   Realpath Usage: 253K

Measured on Wed 2024 Sep 4, when as RC, effective date Mon 2024 Jun 3:

   Page generation time: 0.338
   Total SQL Queries: 225
   Total SQL Cache Hits: 5008
   Total Local Cache Hits: 63
   Total Memcache Hits:
   Memory Usage: 6144K
   Realpath Usage: 304K

Measured on Thu 2024 Aug 29, when as CA, effective date Mon 2024 Jun 3:

   Page generation time: 2.406
   Total SQL Queries: 2489
   Total SQL Cache Hits: 12037
   Total Local Cache Hits: 472
   Total Memcache Hits:
   Memory Usage: 49152K
   Realpath Usage: 193K

Measured on Wed 2024 Sep 4, when as CA, effective date Mon 2024 Jun 3:

   Page generation time: 0.354
   Total SQL Queries: 236
   Total SQL Cache Hits: 8542
   Total Local Cache Hits: 66
   Total Memcache Hits:
   Memory Usage: 6144K
   Realpath Usage: 303K

RETURN