Home/ Questions/Q 6594557
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T17:49:37+00:00

Memory management is not something that most PHP developers ever need to think about.

  • 0

Memory management is not something that most PHP developers ever need to think about. I’m running into an issue where my command line script is running out of memory. It performs multiple iterations over a large array of objects, making multiple database requests per iteration. I’m sure that increasing the memory ceiling may be a short term fix, but I don’t think it’s an appropriate long-term solution. What should I be doing to make sure that my script is not using too much memory, and using memory efficiently?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The golden rule

    The number one thing to do when you encounter (or expect to encounter) memory pressure is: do not read massive amounts of data in memory at once if you intend to process them sequentially.

    Examples:

    • Do not fetch a large result set in memory as an array; instead, fetch each row in turn and process it before fetching the next
    • Do not read large text files in memory (e.g. with file); instead, read one line at a time

    This is not always the most convenient thing in PHP (arrays don’t cut it, and there is a lot of code that only works on arrays), but in recent versions and especially after the introduction of generators it’s easier than ever to stream your data instead of chunking it.

    Following this practice religiously will “automatically” take care of other things for you as well:

    • There is no longer any need to clean up resources with a big memory footprint by closing them and losing all references to them on purpose, because there will be no such resources to begin with
    • There is no longer a need to unset large variables after you are done with them, because there will be no such variables as well

    Other things to do

    • Be careful of creating closures inside loops; this should be easy to do, as creating such inside loops is a bad code smell. You can always lift the closure upwards and give it more parameters.
    • When expecting massive input, design your program and pick algorithms accordingly. For example, you can mergesort any amount of text files of any size using a constant amount of memory.
    • 0