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..
Good day everyone, I have a question related to Spryker Touch feature. We have two imports running -
Good day everyone, I have a question related to Spryker Touch feature. We have two imports running - product import and category import. The imports use facade methods for certain operations, which then execute updates against spy_touch
table. What we’re experiencing is that sometimes simple update query UPDATE "spy_touch" SET "touched"=$1 WHERE "spy_touch"."id_touch"=$2
takes 20 minutes or more. Deeper investigation lead to an assumption that this might be caused by the way how Postgres is doing updates on indexed fields internally. Turns out touched
field is indexed. We have close to 4kk entires in touch table.
Has anyone else experienced similar behaviour and have some hints how to tackle it?
Comments
-
i think most people here never came into contact with the concept of touch and collectors
0 -
but i think you are already giving a good approach on how to handle this in the question
0 -
have you considered dropping (or deactivating) and then recreating the index after the query?
0 -
a big, volatile index can have significant impact on write-heavy scenarios
0 -
In general is this touch concept is needed in newer shops. I've heard somewhere that its kind of an old approach and was replaced by pub&sub? Or am I mistaking something?
0 -
publish&synchronize, correct
0 -
Sorry I meant in OLDER shops
0 -
I wrote newer...
0 -
sure, yes. this concept is not used anymore
0 -
in new projects
0 -
but that does not solve your problem, i guess 😊
0 -
so, i recommend to try bypassing the index during write/update here
0 -
Well if we would remove this package it would be gone.
0 -
and also its functionality would be gone 🤔
0 -
there is probable a reason you still have, no?
0 -
does the above query even take 20 mins when you try to execute it manually against a single id?
0 -
Its there because it was there as a default 1 or 2 years ago. Now we're updating the code base to second latest Spryker release
0 -
It happens randomly
0 -
Few iterations run without a problem, then suddenly it get stuck. Then again back to normal for few iterations and so it goes
0 -
even when executed with the same id?
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 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
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random