Versions Compared

Key

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


...

Overview

While profiling a FOLIO instance running Juniper release, we found out that it is using Mark and Sweep Garbage Collection phases but were not sure which Garbage Collection algorithm it was using. We created

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-201
 - POC  POC to investigate Garbage Collection in FOLIO modules

Overview

Currently, when writing JMeter scripts, we are manually capturing the requests in JMeter script which are triggered by the browser. It works fine for workflows which are relatively small(10-20 requests to backend) but are not feasible if there are 100 or more requests. We should come up with an approach to automate the capturing process.

For example, below query 

GET /instance-storage/instances?query=(item.status.name="In transit") sortby title&limit=100&offset=0

The browser makes a call to at least 20-30 BE requests 

Image Removed

Investigate and come up with alternatives to capture these queries at the browser level and import them to JMeter script.

Requirements

  • Improve JMeter scripts creation process
  • Automate manual steps

...