Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

test /mod-notify/patron-notice API endpoint performance

Description

Per
"Oleksii Maksymov, just a FYI that since this ticket was created, we have narrowed some performance issues related to mod-authtoken and mod-permissions (mostly mod-permissions because mod-authtoken calls mod-permissions). The log provided in this ticket does not show that because at that time the Okapi "requestId" was not passed/logged from module->auth->permissions yet. So if you can directly test /mod-notify/patron-notice API endpoint and proves that it indeed performs good, we can focus on mod-permissions performance. Thanks."

06:33:14 INFO ProxyContext :209 634164/circulation;575977/patron-notice RES 200 3213915us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 06:40:39 INFO ProxyContext :209 819936/circulation;459004/patron-notice RES 200 875307us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:11:21 INFO ProxyContext :209 138484/circulation;987866/patron-notice RES 200 936597us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:29:38 INFO ProxyContext :209 989595/circulation;779990/patron-notice RES 200 948382us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 12:06:29 INFO ProxyContext :209 328653/circulation;408832/patron-notice RES 200 810566us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 13:04:03 INFO ProxyContext :209 400620/circulation;249514/patron-notice RES 200 1004480us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 13:26:41 INFO ProxyContext :209 931043/circulation;428431/patron-notice RES 200 866814us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 13:53:03 INFO ProxyContext :209 241303/circulation;982914/patron-notice RES 200 1145295us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 06:44:42 INFO ProxyContext :209 704181/circulation;787378/patron-notice RES 200 952761us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 10:42:36 INFO ProxyContext :209 867687/circulation;062201/patron-notice RES 200 826621us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:06:00 INFO ProxyContext :209 166292/circulation;635409/patron-notice RES 200 1027861us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:37:52 INFO ProxyContext :209 322342/patron;031092/circulation;545501/patron-notice RES 200 821425us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:43:39 INFO ProxyContext :209 988075/circulation;590651/patron-notice RES 200 727284us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:43:57 INFO ProxyContext :209 266552/circulation;904762/patron-notice RES 200 824278us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 11:52:47 INFO ProxyContext :209 273233/circulation;778663/patron-notice RES 200 1336809us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice 12:06:23 INFO ProxyContext :209 740485/circulation;891459/patron-notice RES 200 1187649us mod-notify-2.3.1 http://pvt.lb.q31f.folio-eis.eu-central-1:8051/mod-notify/patron-notice

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Darcy Branchini February 12, 2021 at 12:50 PM

https://folio-org.atlassian.net/browse/MODNOTIFY-64#icft=MODNOTIFY-64 was created to make a plan for performance testing for notices. This ticket is outdated at this point in time, so new ones will be created once the plan is complete.

Khalilah Gambrell October 8, 2019 at 3:24 PM

and , yes but I need to update the title / description of this story. The team believes they should conduct tests to determine any issues.

Cate Boerema October 8, 2019 at 2:14 PM

Hi , and I were looking at this issue in a meeting today. This is something Vega will be looking into, right?

Hongwei Ji September 30, 2019 at 11:16 AM

, just a FYI that since this ticket was created, we have narrowed some performance issues related to mod-authtoken and mod-permissions (mostly mod-permissions because mod-authtoken calls mod-permissions). The log provided in this ticket does not show that because at that time the Okapi "requestId" was not passed/logged from module->auth->permissions yet. So if you can directly test /mod-notify/patron-notice API endpoint and proves that it indeed performs good, we can focus on mod-permissions performance. Thanks.

Oleksii Maksymov September 30, 2019 at 8:07 AM
Edited

, We would like to clarify some details of the statistics provided.
To understand how to check the result of the improvement, conduct monitoring and accordingly create a report on the results of the improvements made to the modules.
Based on the data presented in the user story CIRC-448, we would like to clarify the requirements for statistics and testing:
1. Monitoring tool.
When debugging the performance of certain API calls, use tool https://github.com/folio-labs/giraffe. Since there are no other possible ways to get log logs in containers.

2. Performance test.
To collect the metrics, the performance test was used - https://github.com/folio-org/folio-perf-test/tree/master/Folio-Test-Plans/core-platform/FOLIO-1811

3. An action or testing process.
"Сheck-in" process.

4. The server on which testing was conducted.
Jenkins https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/254/ build, which runs every time during the test run.

Based on the requirements described above, we will conduct metrics and statistics before and after improvements, right?

Duplicate

Details

Assignee

Reporter

Labels

Priority

Development Team

Vega

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 18, 2019 at 2:11 PM
Updated February 12, 2021 at 12:50 PM
Resolved February 12, 2021 at 12:50 PM
TestRail: Cases
TestRail: Runs

Flag notifications