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..
Hello, we experienced an issue today that might concern us in the future. Our customer has abstract
Hello,
we experienced an issue today that might concern us in the future.
Our customer has abstract products that get drilled down to a concrete product using many super attributes. Today we had 9 in sum, with two options each β¦ which is not that much in my opinion.
However, with 8 attributes we had no problems before, but today with 9 we got a memory allocation issue in the AttributePermutationGenerator while generating the attribute permutations for the product detail page. The limit of 1024MB was exceeded.
So, yes, this one case is solvable increasing the memory limit. But I am worry about further limitations since itβs very likely that we get additional attributes.
Also, this permutation generation stuff seems not to progress linear because the problem at all is not a linear problem. The memory consumption will explode at a specific point.
So my question here: What are the limitations? Any experiences from other projects handling many super attributes?
Best
Comments
-
@UPWG9AYH2 could you create a support ticket for it, we will need to solve this problem.
cc: @valerii.trots0 -
I can confirm that issue
0 -
@UPWG9AYH2 try to make super attributes as simple text types. Without options. If possible. I had the same problem and as i remember it helped
0 -
I'm facing the same issue. Changing the super attributes' type doesn't help.
What's the progress on this one? Is there a ticket number I can refer to?0 -
Check this release please - https://api.release.spryker.com/release-group/3210.
0 -
Doesn't work. After updating the packages, I'm getting redis connect errors. So I tried to resetup the docker env and ended up with this:
Store: AT | Environment: docker.dev Build Yves frontend spryker-b2b-demo-shop@1.0.0 yves /data
0 -
Seems that the shop-ui module depends on a missing npm package.
0 -
Thats some other issue. See https://sprykercommunity.slack.com/archives/CKJRJM5FG/p1607950686484600 for a solution
0 -
Thanks Ingo, you were faster. π
0 -
So the recommended solution is to downgrade the shop-ui and lose updatability? Am I getting it right?
0 -
As far as i can see, the solution is to add the missing dependency to your project level package.json
0 -
You need to fix package.json as
Unfortunately we cannot force npm dependencies update using composer.
0 -
-
thanks for the link @valerii.trots
0 -
Thanks. We're one step further now. But now the Jenkins jobs aren't set up anymore.
0 -
Whats the error message? Seems to me like the usual stuff that happen when updates gettin applied π
0 -
No error message. When I open scheduler.spryker.local, there are no jobs. Even after running
docker/sdk console scheduler:setupmanually.0 -
docker/sdk console scheduler:setup -vvv?0 -
Seems to work now. Here's what I did:
docker/sdk cli composer require filp/whoops spryker/product-storage:"^1.31.0" spryker-shop/product-detail-page:"^3.12.0" spryker/product:"^6.22.1" spryker/product-attribute:"^1.8.1" docker/sdk cli npm install password-validator
It didn't work until I ran the composer update without the --update-with-dependencies option.
I needed to add the filp/whoops package, too, since it was moved to dev dependencies recently, which obviously is wrong.0 -
which obviously is wrong
Nope. It's just a part of some updates\migration path that isn't taken for the project yet.
0 -
At first glance, it looked as if it would work, but it doesn't. Still failing at the same place:
[console] [cli] - [2021-02-09T09:01:29.657080+00:00] Zed.CRITICAL: ErrorException - FATAL ERROR - Allowed memory size of 4294967296 bytes exhausted (tried to allocate 20480 bytes) in "/data/vendor/spryker/product/src/Spryker/Zed/Product/Business/Product/Variant/AttributePermutationGenerator.php::55" {"exception":"[object] (ErrorException(code: 0): FATAL ERROR - Allowed memory size of 4294967296 bytes exhausted (tried to allocate 20480 bytes) at /data/vendor/spryker/product/src/Spryker/Zed/Product/Business/Product/Variant/AttributePermutationGenerator.php:55)0 -
How many super attributes do you use?
0 -
There are products with seven super attributes. There might be even more.
0 -
This "fix" works with at least 9 super attributes.
Could you please provide exact steps to reproduce?@jeremy.fourna FYI.
0 -
I don't think that it's safe to say works with at least x super attributes. It's not only about the number of super attributes, but also the amount of different values. You could have for example two super attributes only, but if each of them is having ten values, things will go crazy again.
And that's my actual issue. The combination of super attributes and their values makes the php memory consumption grow exponentially.The steps that I'm doing are pretty basic. Once I'm having everything in the db, I simply call docker/sdk console publish:trigger-events. In rabbitmq I can see the publish messages coming in and being processed. Once it gets to the abstract product publish messages, it will exceed the memory. The queue is getting stuck then, i. e. it's picking the same bulk of 500 messages over and over again and retries forever.
0 -
My βexperienceβ with this issue was, that the problem is growing more worse with different attributes than with different values.
0 -
I may be wrong but this "fix" has been developed specifically for Ingo's case as a quick win. Proper fix will follow as a big refactoring of the area.
@jeremy.fourna could you confirm this?
0 -
-
@valerii.trots the solution is not supposed to be a quick fix, we normally solved the root cause
0 -
Can't confirm, unfortunately.
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 83 Spryker News
- 965 Developer Corner
- 819 Spryker Development
- 91 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 36 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 29 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 33 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random