<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on Eknix — Web security &amp; performance for the enterprise</title><link>https://www.eknix.com/tags/performance/</link><description>Recent content in Performance on Eknix — Web security &amp; performance for the enterprise</description><generator>Hugo</generator><language>en-us</language><copyright>© {year} EKNIX LTD. All rights reserved.</copyright><lastBuildDate>Tue, 10 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.eknix.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>The CDN math that actually matters for e-commerce</title><link>https://www.eknix.com/blog/cdn-math-ecommerce/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/cdn-math-ecommerce/</guid><description>&lt;p&gt;When we audit a &lt;a href="https://www.eknix.com/solutions/performance-cdn/"&gt;CDN deployment&lt;/a&gt; for an e-commerce client, we don&amp;rsquo;t start with the dashboard the vendor provides. We start with four numbers. If these four numbers aren&amp;rsquo;t being tracked, optimized, and reported every month, the deployment is almost certainly underperforming.&lt;/p&gt;
&lt;h2 id="1-cache-hit-ratio-by-content-type"&gt;1. Cache hit ratio (by content type)&lt;/h2&gt;
&lt;p&gt;The aggregate cache hit ratio is mostly useless — it&amp;rsquo;s dominated by static assets that would cache anywhere. What matters is the cache hit ratio broken down by content type:&lt;/p&gt;</description></item><item><title>How CDN node mapping actually works</title><link>https://www.eknix.com/blog/cdn-node-mapping/</link><pubDate>Mon, 10 Nov 2025 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/cdn-node-mapping/</guid><description>&lt;p&gt;There&amp;rsquo;s an interview question that used to be a rite of passage in backend engineering: &amp;ldquo;Walk me through everything that happens when a user types a URL and hits enter.&amp;rdquo; Most answers got stuck on DNS and TLS. The part most people glossed over — how the request actually lands on the &lt;em&gt;right&lt;/em&gt; CDN node out of thousands distributed globally — is where the interesting engineering lives.&lt;/p&gt;
&lt;p&gt;Get the mapping wrong and your users in Singapore are hitting a PoP in Frankfurt. The latency shows up in your P75 TTFB, in your bounce rate, and eventually in your revenue numbers.&lt;/p&gt;</description></item><item><title>Is Google reCAPTCHA a DDoS Defence? The Cost Math Says No</title><link>https://www.eknix.com/blog/recaptcha-ddos-cost/</link><pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/recaptcha-ddos-cost/</guid><description>&lt;p&gt;There&amp;rsquo;s a category of question that gets asked quietly in Slack channels and in private post-incident reviews: &amp;ldquo;could we just use reCAPTCHA to handle this?&amp;rdquo; It&amp;rsquo;s not an unreasonable instinct. Google reCAPTCHA is already deployed on most sites, it can challenge suspicious traffic, and it costs nothing for the first ten thousand requests. As a lightweight speed bump, it has its place.&lt;/p&gt;
&lt;p&gt;But &amp;ldquo;speed bump against DDoS traffic&amp;rdquo; and &amp;ldquo;speed bump against spam submissions&amp;rdquo; are very different things — and running reCAPTCHA into a volumetric attack has a financial profile that most teams haven&amp;rsquo;t priced out before they need to.&lt;/p&gt;</description></item><item><title>Do You Know How Your Customers Experience Your Site? Or Just Where They Go?</title><link>https://www.eknix.com/blog/akamai-mpulse-real-user-monitoring/</link><pubDate>Thu, 10 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/akamai-mpulse-real-user-monitoring/</guid><description>&lt;p&gt;Most engineering teams I talk to have Google Analytics. A lot of them assume that means they understand how their site is performing. It doesn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;Google Analytics is an excellent tool for answering one set of questions: where do users come from, where do they go, what do they convert on, where do they drop off? It&amp;rsquo;s a behavioural map. It tells you the path. What it doesn&amp;rsquo;t tell you is what the path &lt;em&gt;felt like&lt;/em&gt; — how long it took, how it degraded under load, which users are bouncing not because the content is wrong but because the page took five seconds to load on a 4G connection in Germany.&lt;/p&gt;</description></item><item><title>Is Your Website Ready for the Holiday Rush?</title><link>https://www.eknix.com/blog/holiday-peak-readiness/</link><pubDate>Tue, 03 Dec 2024 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/holiday-peak-readiness/</guid><description>&lt;p&gt;11.11 just happened. Black Friday is right behind it. Then Christmas, then New Year&amp;rsquo;s. If your platform survived Singles Day with headroom to spare, you might be tempted to relax. Don&amp;rsquo;t. Each of these events amplifies the same underlying gaps — and the ones that don&amp;rsquo;t show up under moderate traffic tend to surface spectacularly under peak load.&lt;/p&gt;
&lt;p&gt;The preparation conversation usually focuses on infrastructure scaling: more instances, higher database connection limits, load balancer tuning. That&amp;rsquo;s necessary but not sufficient. Two factors that consistently determine whether a platform has a good or bad holiday season sit outside the application layer entirely: security posture and edge performance.&lt;/p&gt;</description></item></channel></rss>