What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Anyone an idea how to speedup abstract/concrete product requests via GLUE? We have with many abstrac

UMVENKCBF
UMVENKCBF Posts: 38 🧑🏻‍🚀 - Cadet
in Help

Anyone an idea how to speedup abstract/concrete product requests via GLUE? We have with many abstract and concrete products request times > 5 / > 10 seconds?
for example:
• 1 master (abstract product) has about 200 variantes (concrete products) with attributes

Comments

  • Unknown
    Unknown

    hey

  • Unknown
    Unknown

    did you try to profile the request to pin point where you lose the time?

  • Unknown
    Unknown

    do you have an yves in your project? does it behave the same way?

  • UMVENKCBF
    UMVENKCBF Posts: 38 🧑🏻‍🚀 - Cadet

    We are currently on.... seems fetching the abstract / concrets with attributes are the problem.

    Anyone has a production system with many many attributes running?

  • Unknown
    Unknown

    but that should actually already be denormalized in reids at that point, if you did not do too many changes

  • Unknown
    Unknown

    i would suggest to have a look at the client first

  • Unknown
    Unknown

    do you already have a profiler in place?

  • giovanni.piemontese
    giovanni.piemontese Technical Lead @ Löffelhardt Spryker Solution Partner Posts: 871 🧑🏻‍🚀 - Cadet

    in our project we have ca. 7 000 Attributes and ca. 2,5Mio Products. We don't use yet the Glue but read of products from redis is very fast, because as from Marco Podien said, they are already denormalized in redis.

    Can u please provide us more information, where precisly the glue spent a lot of time to fetch the informations?

  • UMVENKCBF
    UMVENKCBF Posts: 38 🧑🏻‍🚀 - Cadet

    Will provide information asap. I will investigate.

    Example:

    • 6MB for master product request
    • 208 concrete product (variants) requests for getting data for product variants

    The problems sums up ...

  • UKHR9UN00
    UKHR9UN00 Posts: 70 🧑🏻‍🚀 - Cadet

    If you don't need all relationships, you can use the include parameter to specify which relationships should be loaded for the request.
    E.g. /abstract-products/ABSTRACT-SKU?include=abstract-product-prices will only load the base abstract product data and the abstract-product-prices relation. Same should work for nested relationships, like stocks for concrete products

  • UKHR9UN00
    UKHR9UN00 Posts: 70 🧑🏻‍🚀 - Cadet

    Additionally you should check if you fire any ZED requests to load the data. E.g. in an earlier release of the tax module, tax sets were loaded from ZED instead of Redis

  • UMVENKCBF
    UMVENKCBF Posts: 38 🧑🏻‍🚀 - Cadet

    Hi, some new information:
    1 abstract product
    112 concrete products

    Most of the time spryker loads/idles with glossary and translation.

Categories