Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.For debugging, it is sometimes very useful to monitor memory usage on cron feed processing.
I propose to monitor memory increase while processing feeds. Will post patch shortly.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 503242-8_new_stats.patch | 2.8 KB | aron novak |
| #8 | 503242-7_new_stats.patch | 2.05 KB | alex_b |
| #7 | 503242_changelog_change.patch | 771 bytes | aron novak |
| #6 | 503242-6_measure_mem.patch | 1.68 KB | alex_b |
| #5 | 503242-5_measure_mem.patch | 1.68 KB | alex_b |
Comments
Comment #1
alex_b commentedComment #2
alex_b commentedComment #3
aron novak(PHP 4 >= 4.3.2, PHP 5) memory_get_usage - php.net
Required: PHP version 4.3.5 or higher - d.o
Then RTBC.
Comment #4
alex_b commentedWhy do we actually only store stats if there are $new items?
Pending: php version checking.
Comment #5
alex_b commentedPatch in #4 contained unrelated changes.
Comment #6
alex_b commentedBetter comment wording.
Comment #7
aron novakLet's explain the change of the meaning of update rate field at the admin interface.
Comment #8
alex_b commentedOk, this is growing out to be a more comprehensive overhaul of the statistics logging:
- Log not only if there are new items
- Log next refresh time
- Log growth in memory usage
Comment #9
aron novakUnified patch of #8 and #7
Seems to be okay.
Comment #10
alex_b commentedRTBC from my point of view, too.
Comment #11
aron novak