CloudFlare has added this nifty chart to give you an idea the performance boost their Argo Smart Networking feature adds (or takes away).
Unfortunately, the statistics are limited to the previous 4 hours, so I’ll try to post a couple separate charts.
Here’s one to start.
Above is a histogram of Time To First Byte (TTFB). The blue and orange series represent the before and after TTFB in locations, Argo found a Smart Route. TTFB measures the delay between Cloudflare sending a request to your server and receiving the first byte in response. TTFB includes network transit time (which Smart Routing optimizes) and processing time on your server (which Argo has no effect on).
The geography of this first sample of Argo users was entirely limited to Moscow, Russia – suggesting over the past 48 hours, CloudFlare’s link to that side of the planet has performed faster. All the data originated from Google’s Northern California Data Center.
Site 2: This site is being served out of AWS East Data Center.
Note a modest improvement in both China and Ireland.
Site 3: This site only had traffic of about 300 MB / 25,000 Requests over the past 48 hours so CloudFlare is unable to display performance data.
Updating your software, you may have come upon the error:
warning: /var/cache/yum/x86_64/latest/modcloudflare/packages/mod_cloudflare-2016.11.0-1.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 8caccbf8: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUDFLARE-MOD_CLOUDFLARE-1
The GPG keys listed for the "mod_cloudflare Packages" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
Failing package is: mod_cloudflare-2016.11.0-1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUDFLARE-MOD_CLOUDFLARE-1
The easy fix for this is to follow the instructions at cloudflare on updating these keys. Just a couple linds of commands to run for most systems. FIX IT!