↑ Return to D00 Server

D07b Performance new Server


Page no: D07b

 

Explanation
Videos and Pics

Issues related to Slow Server

Slow start Snbchf

This video is about slow start of snbchf.com sometimes.

 

The problem is fixed.

Performance on SNBCHF.com

We have very good performance on SNBCHF, but we can improve a lot and to be similar with ecoblogs. In the video, we are talking about the compare of the two of the sites, what we can improve in SNBCHF. And of course about our bigger problem currently – the cdn slow performance.

 

The performance of snbchf.com now is good.

New Performance Issues Website

Again we have slow performance on snbchf

The site takes too much resources

I updated all of the software and restart all services of the server. Now the performance is good again.

Performance issues after moving to new webserver

Issues:

1) The crons
2) All in one security (find a problem)
3) Bad Chinese bots

Statistic with the issues:

1) About 6.6k per second to MySQL
2) About 60mb. per second MySQL traffic
3) CPU on 100% of its resource

Statistic after the issues:

1) About 2k per every 5 seconds to MySQL
2) About 10mb. per second MySQL traffic
3) CPU on 5% of its resource

Performance improvements:

  • Optimize images (sys guy)
  • Enable redis cache (sys guy)
  • Enable compression
  • Minify JavaScript & css files
  • Stop Page cache
  • Stop lazyload
  • Test disable different plugins and see the difference
  • Bad Chinese bots

All of the things in the video are done on Austrian only.

Measures for Improvement

How to Fix “Parallelize Downloads Across Hostnames” Warning

Seeing the “parallelize downloads across hostnames” warning in Pingdom, GTmetrix, or Google PageSpeed Insights? This is because web browsers are limited to the number of concurrent connections they can make to a host. This is mainly due do HTTP/1.1 in which browsers open on average 6 connections per hostname. This warning is typically seen on websites with a large number of requests. In the past, the only way to get around this limitation is to implement what they call domain sharding.

Parallelize Downloads Across Hostnames
Parallelize Downloads Across Hostnames

- Click to enlarge

[note]

Note: If you are running over HTTPS with a provider that supports HTTP/2, this warning can usually be safely ignored now. With HTTP/2 multiple resources can now be loaded in parallel over a single connection.

[/note]

Depending upon the tool or software reporting it, the warning might appear in a couple different ways:

  • “parallelize downloads across hostnames”
  • “increase download parallelization by distributing these requests across multiple hostnames”

If you are still running over HTTP and haven’t migrated to HTTP/2 yet, you can follow the tutorial below on how to implement domain sharding. Again, most of the techniques are now considered deprecated. Over 77% of browsers now support HTTP/2 when running over HTTPS, as well as many CDN and web hosting providers, including Kinsta. It is also important to note that Pingdom doesn’t support HTTP/2 yet since it uses an older version of Chrome.

Pingdom Parallelize Downloads Across Hostnames
Pingdom Parallelize Downloads Across Hostnames

- Click to enlarge

Fix “Parallelize Downloads Across Hostnames” Warning

Domain sharding refers to spreading out your assets across multiple subdomains. By doing this you can multiply the number of simultaneous requests. Using domain sharding also gives you the ability to load content on cookie-free subdomains. However, it is also important to note that there are a couple drawbacks to this. By introducing additional subdomains you are adding more DNS requests which increases resolution times and you lose a lot of your caching benefits. Follow the steps below to set it up.

1. Setup Additional Subdomains

The first thing you will need to do is create additional subdomains and or CNAME records to spread across the request for your static assets. You can do this at your DNS registrar or if you are a Kinsta customer you can also edit your DNS records from within your MyKinsta dashboard. Typically no more than 4 are recommended. You will want to point your additional CNAMEs at your /wp-content directory. An example of a configuration might be:

domain.com
static1.domain.com
static2.domain.com
static3.domain.com

2. Edit WordPress Config

You then have to configure WordPress to parallelize the downloads across subdomains. Simply add the following code to your WordPress theme’s functions.php file (src: GitHub). And replace the $subdomains values with your subdomains. All subdomains/hostnames MUST have the same structure/path.

This same technique above can also be used with CDN providers such as KeyCDN, MaxCDN, and CloudFlare to fix the “parallelize downloads across hostnames” warning. However, almost all CDN providers now support HTTP/2 in which domain sharding is not recommended. And you can still serve assets from a CDN via HTTPS even if you haven’t migrated your WordPress site yet to HTTPS.

All subdomains/hostnames MUST have the same structure/path.
All subdomains/hostnames MUST have the same structure/path.

- Click to enlarge

Austrian from New York Very Good Cached

Q: Isn’t the site cached? So we should have a better performance.

A: Yes, it has 2 level of cache.

Austrian from New York Very Good Cached
Austrian from New York Very Good Cached

- Click to enlarge

 

Performance Tests July 01

Central Banks
1.5 MB

831 ms

Central banks - 01-Jul-16
centralbanks - 01-Jul-16

- Click to enlarge

European 11.7 MB, 1.12 sec

European - 01-Jul-16
European - 01-Jul-16

- Click to enlarge

One page in European

11.9 MB, 880 ms

European page - 01-Jul-16
European page - 01-Jul-16

- Click to enlarge

Leaders 5.6 MB, 1.02 sec (stockholm)

2020 Nov: Leaders 9.8MB, 9.81 seconds (London)

Leaders - 01-Jul-16
Leaders - 01-Jul-16

- Click to enlarge

Syndication
1.6 MB, 895 ms

Syndication - 01-Jul-16
Syndication - 01-Jul-16

- Click to enlarge

SNBCHF.com

3.8 MB, 1.91 sec, Faster than 74%

snbchf - 01-Jul-16
snbchf - 01-Jul-16

- Click to enlarge

For comparison

FAZ.NET 3.7MB, 4.52 sec, Faster than 37%

faz.net - 01-Jul-16
faz.net - 01-Jul-16

- Click to enlarge

Performance Tests June 26

Central Banks
0.38 MB

60 Sec

Central banks 0.4 MB 60 Sec - June 26, 2016
Central banks 0.4 MB 60 Sec - June 26, 2016

- Click to enlarge

European 11.9 MB, 21 sec

European 21sec 12MB - June 26, 2016
European 21sec 12MB - June 26, 2016

- Click to enlarge

One page in European

11.7 MB, 17.4 sec

European page 17 sec 12MB - June 26, 2016
European page 17 sec 12MB - June 26, 2016

- Click to enlarge

Leaders 5.6 MB, 3.52 sec

Leaders 5.6 MB 3.5 Sec - June 26, 2016
Leaders 5.6 MB 3.5 Sec - June 26, 2016

- Click to enlarge

Syndication
1.6 MB, 3.38 sec, faster than 49%

Syndication 1.6 MB 3.38 sec - June 26, 2016
Syndication 1.6 MB 3.38 sec - June 26, 2016

- Click to enlarge

SNBCHF.com

7.7 MB 3.40 sec, faster than 49%

SNBCHF 11MB 3.40Sec - June 26, 2016
SNBCHF 11MB 3.40Sec - June 26, 2016

- Click to enlarge

For comparison

FAZ.NET  3.3MB, 3.47 sec, Faster than 48%

Faz 3.4 sec 3.3MB - Jun 26, 2016
Faz 3.4 sec 3.3MB - Jun 26, 2016

.

 

See more for D0x Server