...
The following table shows the slow 75th percentile APIs taking more than 100 ms to return, and also comparing them against Goldenrod's. Other than the 1-user test, starting with the 5-users test, all listed APIs are slower with GET automated-patron-blocks leading the way at 150% slower, while GET circulation/loans regressed up to 60%
Note: GR = Goldenrod build, HS = Honeysuckle build
API | 1 user GR (75th %tile) | 1 user HS (75th %tile) | 5 users GR (75th %tile) | 5 users HS (75th %tile) | 8 users GR (75th %tile) | 8 users HS (75th %tile) | 20 users GR (75th %tile) | 20 users HS (75th %tile) |
|---|---|---|---|---|---|---|---|---|
| GET circulation/loans | 0.345 | 0.349 | 0.365 | 0.406 | 0.075 | 0.122 | 0.654 | 0.784 |
| GET inventory/items | 0.208 | 0.186 | 0.208 | 0.222 | 0.225 | 0.244 | 0.312 | 0.375 |
POST checkin-by-barcode | 0.682 | 0.593 | 0.631 | 0.664 | 0.815 | 0.874 | 1.296 | 1.467 |
| POST checkout-by-barcode | 0.750 | 0.717 | 0.688 | 0.784 | 0.733 | 0.877 | 1.205 | 1.469 |
| GET automated-patron-blocks | 0.069 | 0.163 | 0.085 | 0.180 | 0.079 | 0.197 | 0.118 | 0.296 |
...
This table shows that the average response time of the checkout transaction is 9% to 28% slower than in Goldenrod, and check-in in Honeysuckle likewise is about 4-22% slower (data aggregated from 5 to 20 users test runs).
Update 1/14/2011
- Subsequent investigations (
ANDJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-140
) on GET /circulation/loans do not show degradations by the API itself. We hypothesize that other API calls that were executed during the test run may have dragged down the response time, particularly if it was trying to read and write to the same rows in the database at the same time.Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-1014
Longevity test
A 24-hour longevity test was performed with 20 concurrent users and running with Okapi 4.2.2. Key observations:
...