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

The Published Content API has become significantly slower in 15.1.0-rc2 #17768

Closed
DanielToft opened this issue Dec 10, 2024 · 2 comments
Closed

Comments

@DanielToft
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.1.0-rc2

Bug summary

After upgrading from 15.1.0-rc to 15.1.0-rc2, I have noticed that the Published Content API has become significantly slower.

My API endpoint, where I run a query on about 500 child nodes, used to take 30-50ms and now takes 800ms-1sec to execute.

I'm querying on MultiNodeTreePicker, TrueFalse and Textstring properties.

IPublishedContent content = GetContent()

edition
    .Children() // 500 nodes
    .Where(x => ...)
    .Skip(0)
    .Take(30)
    .Select(x => ...)
    .ToArray()

I have testet with and without Redis Distributed cache and there is no difference.

Specifics

No response

Steps to reproduce

  • Create approximately 500 nodes
  • Create content on these nodes using MultiNodeTreePicker, TrueFalse and Textstring properties
  • Query the nodes and properties and measure execution time

Expected result / actual result

The execution time will be between 30ms - 70ms

Copy link

Hi there @DanielToft!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@Zeegaan
Copy link
Member

Zeegaan commented Dec 12, 2024

Fixed in #17779 😁

@Zeegaan Zeegaan closed this as completed Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants