Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom asset definitions add noticeable request performance hit #18304

Closed
cconard96 opened this issue Nov 13, 2024 · 2 comments · Fixed by #18454
Closed

Custom asset definitions add noticeable request performance hit #18304

cconard96 opened this issue Nov 13, 2024 · 2 comments · Fixed by #18454
Assignees

Comments

@cconard96
Copy link
Contributor

cconard96 commented Nov 13, 2024

I've noticed that as I add more custom asset definitions for testing (or from running E2E tests locally), almost every request to a PHP script has gotten nearly 10x slower than what it is in 10.0/bugfixes. Currently, I have 70 asset definitions with a few custom fields in each. It isn't clear yet if the issue is the number of definitions, number of custom fields, specific capacities, or a combination of everything.

@cconard96 cconard96 changed the title Request performance slower than 10.0 Custom asset definitions add noticeable request performance hit Nov 13, 2024
@cconard96
Copy link
Contributor Author

Identified the IsInventoriableCapacity as the source of the performance hit. I only had a single asset definition with it enabled and it alone was adding 550ms to the response times.

@AdrienClairembault
Copy link
Contributor

I confirm on my side too.

Without IsInventoriableCapacity:
Image

With one IsInventoriableCapacity:
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants