Make simpletest fail a test when it detects pages that need more than 64MB

Created on 26 May 2015, over 10 years ago
Updated 6 August 2025, about 1 month ago

Problem/Motivation

Over in πŸ“Œ [meta-6] Reduce cold cache memory requirements Closed: outdated we're tracking fixing instances where we exceed the 64MB memory limit.
I asked if we'd like simpletest to try and help us find such pages.

Proposed resolution

Add a header for peak memory usage when running the child site.
Have the parent runner read it and fail tests when it exceeds 64Mb.
Let tests opt-out.

Beta phase evaluation

<!--Uncomment the relevant rows for the issue. -->

Remaining tasks

Most of it

User interface changes

None

API changes

None

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

simpletest.module

Created by

πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

Live updates comments and jobs are added and updated live.
  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

  • πŸ‡¬πŸ‡§United Kingdom catch

    I think this is still relevant, it would be good if we could e.g. monitor how much memory the permissions page uses, cold cache requests etc.

    One way to start with this would be to add memory usage support to performance tests - the performance_test module already collects data at the end of the request, so we should be able to get peak memory usage there. Main question would be how big the range would need to be to avoid false positives. This would have a lot less coverage than doing it globally but we already know what some specific good/bad scenarios are.

  • πŸ‡«πŸ‡·France andypost

    Moreover new APCu 5.1.25 version is out with big changes about memory management and huge pages specifically

Production build 0.71.5 2024