<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Jetpack on Luis Sousa Blog</title>
		<link>https://blog.nuvai.cloud/tags/jetpack/</link>
		<description>Recent content in Jetpack on Luis Sousa Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sat, 13 Jun 2026 10:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.nuvai.cloud/tags/jetpack/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Why wp-admin Was Painfully Slow on a 4-Worker WordPress Docker Stack</title>
				<link>https://blog.nuvai.cloud/posts/wp-admin-slow-apache-workers-jetpack-recursion/</link>
				<pubDate>Sat, 13 Jun 2026 10:00:00 +0000</pubDate>
				<guid>https://blog.nuvai.cloud/posts/wp-admin-slow-apache-workers-jetpack-recursion/</guid>
				<description>&lt;p&gt;We run a travel blog (&lt;a href=&#34;https://joyofexploringtheworld.com/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;joyofexploringtheworld.com&lt;/a&gt;) on a memory-constrained Docker stack behind Traefik. If wp-admin feels fine on a quiet morning and then turns to treacle the moment you open the block editor, the problem is rarely “WordPress is slow.” It is usually &lt;strong&gt;capacity math&lt;/strong&gt; — and sometimes a single filter hook that eats 1.5 GB of RAM.&lt;/p&gt;&#xA;&lt;p&gt;This is what we found on production with two WordPress replicas, each with &lt;strong&gt;four Apache prefork workers&lt;/strong&gt; and a &lt;strong&gt;1536M PHP memory limit&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
