You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2019. It is now read-only.
As a developer,
I want to optimize the graphql data retrieval framework for category queries
so that
I can improve the response times at scale.
Every query optimization must follow the following steps.
Deploy the existing version on cloud starter.
Run Blazemeter perf test for the query with 50 concurrent users.
Optimize the data retrieval framework for the query.
Deploy the changes to cloud starter.
Rerun the perf test in step 2 again and document the findings.
Merge the changes to mainline and deploy to cloud pro.
Run the perf test on cloud pro with 5000 concurrent users.
The text was updated successfully, but these errors were encountered:
@nrkapoor
Please, review the description from initial ticket
The category query should include a filter argument, similar to the products query. It should achieve parity with the REST API's search criteria functionality on category entities.
AC
User is able to filter categories by
id
name
description
isAnchor: return only categories that are isAnchor=yes or isAnchor=no
level: return only categories that are on the specified level in the tree
parentId: return only direct children of the specified parent category
Endpoint accepts new filter criteria, and returns an array of matching CategoryTree objects
As a developer,
I want to optimize the graphql data retrieval framework for category queries
so that
I can improve the response times at scale.
Every query optimization must follow the following steps.
Deploy the existing version on cloud starter.
Run Blazemeter perf test for the query with 50 concurrent users.
Optimize the data retrieval framework for the query.
Deploy the changes to cloud starter.
Rerun the perf test in step 2 again and document the findings.
Merge the changes to mainline and deploy to cloud pro.
Run the perf test on cloud pro with 5000 concurrent users.
The text was updated successfully, but these errors were encountered: