Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

This document contains the results of testing List App refreshing of 200k records on multiple tenants with R/W split enabled (Poppy release). The goal of testing is to assess the performance of mod-lists with load spread across multiple tenants.

...

TransactionSingle tenant*3 tenants**

[Orchid]

10 users

[Poppy]

10 users

[Poppy]

10 users

Testing in parallel with DI and CICO

[Poppy]

R/W split enabled

3 users

[Poppy]

R/W split enabled

10 users

[Poppy]

R/W split enabled

30 users

ListApp refresh, avg

from 9 min 40 sec to

10 min 40 sec

8.5 min17.7 min1.5 min2.3 minInternal servel server error

* Query used in lists - "Item status == Checked out". List refresh result is 200K records.

**Query used in lists - "Item status != Available". List refresh result is about 200K records.


Instance CPU Utilization

Image Modified

Service CPU Utilization

During the 10 users test CPU utilization reached 200% for for mod-fqm-manager, 111% for mod-lists.

Image Modified

Memory Utilization

Memory utilization for mod-permissions increased from 48% to 76% during the tests. 

Image ModifiedImage Modified

DB CPU Utilization

Maximum DB CPU utilization reached 83% (writer instance) and 99% (reader instance) during 30 users test.

Image Modified

DB Connections

DB Load

TOP SQL

Long-running queries: 

Code Block
languagesql
select id from [tenant]_mod_fqm_manager.drv_item_callnumber_location where lower(cast(item_status as varchar)) <> lower($1)
parameters: $1 = 'Available'

...