Posts tagged with memory
– chriswhite.is - submitted by Chris White
I'll show you how to generate a ZIP export of an arbitrary numbers of files in an S3 bucket in a fast and memory efficient way, so you don't go OOM.
Read more [chriswhite.is]
– doeken.org - submitted by Doeke Norg
Yield better results by iterating over generators. Learn more about these supercharged arrays that can preserve memory.
Read more [doeken.org]
Join 9,500+ smart developers
Every month I share what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
Larry Garlfriend explains how you can use PHP 8's weak maps to implement a self cleaning cache. Pretty sweet!
Read more [platform.sh]
On the Tideways blog, Benjamin Eberlei explains PHPs garbage collection internals.
It's helpful to have a broad understanding of how garbage collection works in PHP, along with how you can interact with it so that you can create high performing applications.
Read more [tideways.com]
? If you need to process a lot of models, don't load them all into memory, but chunk them.
— Freek Van der Herten ? (@freekmurze) August 21, 2019
Laravel has a beautiful `each` method for this.https://t.co/cVWdpsGtQ1#laravel #php pic.twitter.com/ISW7XQcehx
Read more [twitter.com]
In a new blogpost published at Sitepoint, Christopher Pitt explores the various ways you can handle reading big files in PHP.
Though this isn’t a problem we frequently suffer from, it’s easy to mess up when working with large files. In asynchronous applications, it’s just as easy to bring the whole server down when we’re not careful about memory usage.
This tutorial has hopefully introduced you to a few new ideas (or refreshed your memory about them), so that you can think more about how to read and write large files efficiently. When we start to become familiar with streams and generators, and stop using functions like file_get_contents: an entire category of errors disappear from our applications. That seems like a good thing to aim for!
Mark Baker made some fascinating benchmarks on the performance of PHP 7's anonymous classes.
A week or so ago, I published an article entitled “In Search of an Anonymous Class Factory” about my efforts at writing a “factory” for PHP7’s new Anonymous Classes (extending a named concrete base class, and assigning Traits to it dynamically); and about how I subsequently discovered the expensive memory demands of my original factory code, and then rewrote it using a different and (hopefully) more memory-efficient approach.https://markbakeruk.net/2016/05/12/anonymous-class-factory-the-results-are-in/Since then, I’ve run some tests for memory usage and timings to assess just how inefficient my first attempt at the factory code was, and whether the new version of the factory really was better than the original.
Because the properties for the object are predefined PHP no longer has to store the data in a hashtable, but instead can say that `$foo` is property 0, `$bar` is property 1, `$baz` is property 2 and then just store the properties in a three-element C array.https://gist.github.com/nikic/5015323This means that PHP only needs one hashtable in the class that does the property-name to offset mapping and uses a memory-efficient C-array in the individual objects. Arrays on the other hand need the hashtable for every array.