Shakiba Moshiri
  • Shakiba Moshiri (شکیبا مشیری)
  • opt
    • high traffic site optimization
      • infrastructure check
      • infrastructure test
  • tools
    • Cryptsetup
      • Container encryption using cryptsetup
    • curly
      • ftp
      • ssl
      • http
      • dns
      • ip
      • email
    • SSH
      • ssh password-less login
        • Untitled
    • volumes and FS
      • installing Gluster fs on Ubuntu 18.04 server
      • Accessing Gluster FS from the client machine
  • CDN
    • How does a CDN work
  • Server Panel
  • DirectAdmin
    • DirectAdmin through a reverse proxy
  • Web Server
    • Nginx
      • Live Steaming with Nginx and FFMPEG
  • Security
  • Container
    • Docker Networking 101
      • why docker networking is important?
      • type of networking in docker
    • Docker
      • How to run gitlab-runner with docker
      • using vim inside any container without installing it
      • Cannot connect to the Docker daemon at unix:///var/run/docker.sock
      • moving docker images around using ssh and pipe
      • How can I make docker-compose pull images using a socks5 proxy?
  • Stack Overflow
  • Github
  • vmware
    • tools
      • how to install vmware CLI govc on Linux
  • Windows
    • How to Erase a Recovery Partition in Windows
Powered by GitBook
On this page

Was this helpful?

  1. opt

high traffic site optimization

Tools, techniques, principles, patterns and designs to have a high-performance Linux server.

PreviousShakiba Moshiri (شکیبا مشیری)Nextinfrastructure check

Last updated 4 years ago

Was this helpful?

Two main approaches to apply optimization

Here are two ways to try to optimize a website; we have top-down and bottom-up. in top-down approach people debate about which programming language is faster. They say WordPress is slow and ReactJS is faster; which is true. Python is faster and NodeJS, yes true. So the point is, for having a really fast website, just a faster programming language cannot help so much. For any website to function (be loaded) we have these four levels (layers):

  1. code level (php, go, python, etc)

  2. service level (Apache, Nginx, LiteSpeed, etc)

  3. architecture level (HA, LB, etc)

  4. infrastructure level (network, dedicated server, VM, containers, etc)

We tested and realized that the same code, but in different DataCenter has different speed. Just changing the DataCenter. So when we can apply optimization from top to bottom (which works) we can apply it from bottom-to-up which is more effective.

We are going to cover these four layers and provide solutions for each laster and improve overall performance of the website we have.

NOTE SVGs are used to better demonstration.

Here is the ineffective approach (top-down)

and here is the effective approach (bottom-up)