I faced a problem when upgrading this module to 1.2, and thought I would write what I found here in case someone else runs into it.

This is a site with about 12,600 nodes, and 25,000+ rows in the nodewords table, mainly just keyword and description for each of the nodes.

Because one of the updates does "SELECT * FROM {nodewords}", this takes a lot of memory, and the update bombs out.

I increased php's memory_limit from 48M to 64M, then 96M, then 128M, and it did not run until I had it all the way up to 256M. Only then was I able to complete the update.

It is best if the module uses batching for this, so as not to blow out memory.

After that, I had to enable the basic module, and then clear the cache from admin/settings/performance

Things were normal after that.

Comments

hass’s picture

hass commented
Title: update.php does not run until PHP memory increased » update.php may fail on big sites for PHP timeout and/or memory reasons
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 6.x-1.2 » 6.x-1.x-dev

I will change the update functions that execute long database operations in multi-pass update functions.

I am changing the referring version to the one that can be changed.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

The update functions that makes changes on the database table are changed to be multi-pass functions. This should resolve both the timeout, and the memory problems.

Status: Fixed » Closed (fixed)

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