Hi,

I'm using this module with some success, but have found that I can't get any of the re-index/clear index functionality to work as I'm hitting memory_limit and max_execution_time limits. I think the solution is to make trackItemChange a batch operation, but just checking if anyone has any better ideas before going down this path.

Thanks,
Anthony.

Comments

das-peter’s picture

I think the solution is to make trackItemChange a batch operation, but just checking if anyone has any better ideas before going down this path.

That was my idea too. However, I couldn't find the time to work on this. Would be absolutely great if you could figure out how to put that into a batch :)

malks’s picture

Hi das-peter,

I ended up not using your module, but stole adapted many of the features from it as I needed most of the funtionality but also needed to extend it for our specific use case. Having said that I did end up having to work out how to batch the trackItemChange and I'm pretty sure I could retrofit into your module. Is this something you would like done still? How do I go about it? i.e. fork and pull against your dev repo?

Thanks,
Anthony.

das-peter’s picture

Is this something you would like done still?

Absolutely :)

How do I go about it? i.e. fork and pull against your dev repo?

Whatever you'd prefer and produces a patch that can be applied to the module ;)
As I don't know the code I can't tell you if it can be done using git or if you've to do it manually.

das-peter’s picture

Issue summary: View changes
Status: Active » Fixed

I've just committed an enhancement for the whole re-index / clear index methods.
The generation of the permutations is now done using the queue and cron. Further I've replaced entity_load() wherever possible by Entity Field Query which hopefully drastically reduces the required processing & memory consumption.
There are also new / adjusted drush commands:

  • sapi-gpq will process the items in the permutation queue.
  • sapi-gg uses the permutation queue now. If you abort it's execution you should be able to continue the processing later with sapi-gpq - or cron will do it for you.

For now I didn't adjust the method trackItemChange(). Let's see if this method really becomes such and amount of entities to process that we need to use an extra queue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.