- 🇳🇱Netherlands seanB Netherlands
We just added a 2.x version of the module. This is a complete rewrite based on plugins to determine which revisions can be deleted. It also uses a queue worker to actually delete revisions. Could you please test if this solves the timeout issues you currently experience?
- 🇳🇴Norway steinmb
We have an older D7 site that also give me grief, 4GB memory is not enough on 7.x-3.2. No timeouts, but run out of memory and is a general performance problem.
Entering this part consume a lot of memory.
```
module_invoke($module = 'node_revision_delete', $hook = 'cron')```
To allow cron to finish I had to return early.
function node_revision_delete_cron() { return;
Just to make sure the rest of the cron tasks works as expected.
- 🇬🇪Georgia almador
what about 28 000 000 rows in node_revision_body and 8 more revision-related tables?
so I have 9 tables, and every table contains around 30 000 000 records, how to speed up the process and make it work with this module way faster?
- Status changed to Closed: outdated
9 months ago 6:44am 7 March 2024 - 🇨🇦Canada adriancid Montreal, Canada
Closing because the current development is being made in branch 2.x