Download as PDF, PPTX
![add_action( 'shutdown', function() {
$line = json_encode( array(
'timestamp' => time(),
'request_uri' => $_SERVER['REQUEST_URI'],
'peak_memory' => memory_get_peak_usage(),
) );
file_put_contents( '/tmp/php-memory.log',
$line . PHP_EOL, FILE_APPEND | LOCK_EX );
});](https://image.slidesharecdn.com/wcsof-konstantin-kovshenin-memory-4-161022100918/75/Memory-Management-in-WordPress-52-2048.jpg)
Uploaded byKonstantin Kovshenin
Memory Management in WordPress
The document discusses strategies for managing memory usage in PHP, particularly within WordPress environments. It highlights the importance of monitoring memory consumption through various tools and advises on coding practices to prevent memory exhaustion errors. Recommendations include profiling techniques, optimizing database queries, and configuring memory limits effectively.
More Related Content
Similar to Memory Management in WordPress
Memory Management in WordPress
- 1. Keep Your Memory UnderControl Konstantin Kovshenin konstantin.blog
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. Zend Memory Manager OSKernel foo.php $a = 5; malloc, mmap, ...
- 14. memory_get_usage() memory_get_peak_usage() Debug Bar, QueryMonitor Memory Usage
- 15. $before = memory_get_usage(); //Do something $after = memory_get_usage(); echo $after - $before;
- 16. Environment loaded Init action Shutdownaction 12.9 MB 14.1 MB 14.4 MB
- 17. 12.9 MB 14.1 MB 14.4MB 12.9 MB 27.3 MB 28.6 MB Environment loaded Init action Shutdown action
- 18. Fatal error: Allowedmemory size of 134217728 bytes exhausted
- 19. ... tried toallocate 8552 bytes in /path/to/wp-includes/wp-db.php on line 1775
- 20. ... tried toallocate 8552 bytes in /path/to/wp-includes/wp-db.php on line 1775 1775: while ( $row = mysqli_fetch_object( ...
- 21. ... tried toallocate 8552 bytes in /path/to/wp-includes/wp-db.php on line 1775 1775: while ( $row = mysqli_fetch_object( ...
- 22.
- 23.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33. 1. Fine-tune theOOM 2. Add more Swap memory
- 34. 1. Fine-tune theOOM 2. Add more Swap memory 3. Figure things out
- 35. ... tried toallocate 8552 bytes in /path/to/wp-includes/wp-db.php on line 1775
- 36.
- 37. Call Stack: 34032184 6.do_action() .../htdocs/wp-settings.php:393 34925000 7. call_user_func_array:{}() .../wp-includes/plugin.php:525 34925104 8. my_plugin_init() .../wp-includes/plugin.php:525 134139664 9. wpdb->query() .../wp-content/plugins/memory.php:25 134172496 10. mysqli_fetch_object() .../wp-includes/wp-db.php:1775
- 38.
- 39.
- 40.
- 41.
- 42. // Pretty bad $posts= get_posts( array( 'posts_per_page' => -1, // ... ) ); foreach ( $posts as $post ) { // ... }
- 43. // A littlebetter $paged = 1; while ( $posts = get_posts( array( 'posts_per_page' => 100, 'paged' => $paged++, ) ) ) { foreach ( $posts as $post ) { // ... } }
- 44. // Good wp_suspend_cache_addition( true); $paged = 1; while ( $posts = get_posts( array( 'posts_per_page' => 100, 'paged' => $paged++, ) ) ) { // foreach ... } wp_suspend_cache_addition( false );
- 45.
- 46.
- 47.
- 48. // Not sogood ob_start( 'ob_callback' ); // Much better ob_start( 'ob_callback', 1024*1024*2 ); function ob_callback( $content, $phase ) { // ... }
- 49.
- 50.
- 51. Monitoring top, free cat /proc/meminfo cat/proc/pid/{status,maps}
- 52. add_action( 'shutdown', function(){ $line = json_encode( array( 'timestamp' => time(), 'request_uri' => $_SERVER['REQUEST_URI'], 'peak_memory' => memory_get_peak_usage(), ) ); file_put_contents( '/tmp/php-memory.log', $line . PHP_EOL, FILE_APPEND | LOCK_EX ); });
- 53.
- 54.
- 55. 1. Choose theright context
- 56. 2. Profile withlarge datasets
- 57. 3. Keep consumption undercontrol
- 58.
- 59. Attributions: Success Kid (SammyGriner): https://en.wikipedia.org/wiki/Success_Kid Ninja character: http://www.vecteezy.com/vector-art/88129-ninja-vector-set Blood spatter CC-Attr-ShareALike 4.0: http://www.freevector.com/splattered-blood-graphics-set User icons by FontAwesome, SIL OFL 1.1: http://fontawesome.io