mirror of
https://github.com/cheatsnake/backend-cheats.git
synced 2024-11-30 11:14:17 +03:00
translated topic about optimization
This commit is contained in:
parent
5bf1aeff26
commit
c4d0620242
@ -2147,28 +2147,74 @@ Testing is the process of assessing that all parts of the program behave as expe
|
|||||||
|
|
||||||
- ### Profiling
|
- ### Profiling
|
||||||
|
|
||||||
|
[Profiling](<https://en.wikipedia.org/wiki/Profiling_(computer_programming)>) is an attempt to find bottlenecks in your code. Profiling allows you to analyze your code and find its longest running sections. The tool used to analyze performance is called a profiler.
|
||||||
|
|
||||||
<details>
|
<details>
|
||||||
<summary>🔗 <b>References</b></summary>
|
<summary>🔗 <b>References</b></summary>
|
||||||
|
|
||||||
</details>
|
1. 📺 [**Optimize Your Python Programs: Code Profiling with cProfile** – YouTube](https://youtu.be/BZzb_Wpag_M)
|
||||||
|
2. 📺 [**A New Way to Profile Node.js** – YouTube](https://youtu.be/ASv8188AkVk)
|
||||||
|
3. 📺 [**Go (Golang) Profiling Tutorial** – YouTube](https://youtu.be/HEwSkhr_8_M)
|
||||||
|
</details>
|
||||||
|
|
||||||
<div align="right"><a href="#top">Contents ⬆️</a></div>
|
<div align="right"><a href="#top">Contents ⬆️</a></div>
|
||||||
|
|
||||||
- ### Caching
|
- ### Caching
|
||||||
|
|
||||||
|
[Caching](https://aws.amazon.com/caching) is one of the most effective solutions for optimizing the performance of web applications. With caching, you can reuse previously received resources (static files), thereby reducing latency, reducing network traffic, and reducing the time it takes to fully load content.
|
||||||
|
|
||||||
|
<p align="center"><img src="./files/optimization/cdn_eng.png" alt="CDN"/></p>
|
||||||
|
|
||||||
|
- [CDN (Content Delivery Network)](https://en.wikipedia.org/wiki/Content_delivery_network)
|
||||||
|
> A system of servers located around the world. Such servers allow you to store duplicate static content and deliver it much faster to users who are in close geographical proximity. Also when using CDN reduces the load on the main server.
|
||||||
|
- Browser-based (client-side) caching
|
||||||
|
> Based on loading pages and other static data from the local cache. To do this, the browser (client) is given special headers: [304 Not Modified](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304), [Expires](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires), [Strict-Transport-Security](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security).
|
||||||
|
- [Memcached](https://en.wikipedia.org/wiki/Memcached)
|
||||||
|
> A daemon program that implements high-performance RAM caching based on _key-value_ pairs. Unlike [Redis](#redis) it cannot be a reliable and long-term storage, so it is only suitable for caches.
|
||||||
|
|
||||||
<details>
|
<details>
|
||||||
<summary>🔗 <b>References</b></summary>
|
<summary>🔗 <b>References</b></summary>
|
||||||
|
|
||||||
</details>
|
1. 📺 [**How Caching Works? | Why is Caching Important?** – YouTube](https://youtu.be/ASP7O5fDpSg)
|
||||||
|
2. 📺 [**Basic Caching Techniques Explained** – YouTube](https://youtu.be/ccemOqDrc2I)
|
||||||
|
3. 📺 [**HTTP Caching with E-Tags - (Explained by Example)** – YouTube](https://youtu.be/TgZnpp5wJWU)
|
||||||
|
4. 📺 [**What Is A CDN? How Does It Work?** – YouTube](https://youtu.be/RI9np1LWzqw)
|
||||||
|
5. 📺 [**Everything you need to know about HTTP Caching** – YouTube](https://youtu.be/HiBDZgTNpXY)
|
||||||
|
6. 📺 [**Memcached Architecture - Crash Course with Docker, Telnet, NodeJS** – YouTube](https://youtu.be/NCePGsRZFus)
|
||||||
|
</details>
|
||||||
|
|
||||||
<div align="right"><a href="#top">Contents ⬆️</a></div>
|
<div align="right"><a href="#top">Contents ⬆️</a></div>
|
||||||
|
|
||||||
- ### Load balancing
|
- ### Load balancing
|
||||||
|
|
||||||
|
<p align="center"><img src="./files/optimization/load-balancer_eng.png" alt="CDN"/></p>
|
||||||
|
|
||||||
|
When the entire application code is maximally optimized and the server capacity is reaching its limits, and the load keeps growing, you have to resort to the [clustering]() and [balancing]() mechanisms. The idea is to combine groups of servers into clusters, where the load is distributed between them using special methods and algorithms, called balancing.
|
||||||
|
|
||||||
|
- Balancing at the network level
|
||||||
|
> - **DNS Balancing**. For one domain name is allocated several IP-addresses and the server to which the request will be redirected is determined by an algorithm [Round Robin]().
|
||||||
|
> - **Building a [NLB cluster]()**. Used to manage two or more servers as one virtual cluster.
|
||||||
|
> - **Balancing by territory**. An example is the [Anycast mailing method]().
|
||||||
|
- Balancing on the transport level
|
||||||
|
> Communication with the client is locked to the balancer, which acts as a proxy. It communicates with servers on its own behalf, passing information about the client in additional data and headers. Example – [HAProxy]().
|
||||||
|
- Balancing at the application level
|
||||||
|
> The balancer analyzes client requests and redirects them to different servers depending on the nature of the requested content. Examples are [Upstream module in Nginx]() (which is responsible for balancing) and [pgpool]() from the PostgreSQL database (for example, it can be used to distribute read requests to one server and write requests to another).
|
||||||
|
- Balancing algorithms
|
||||||
|
> - [**Round Robin**](). Each request is sent in turn to each server (first to the first, then to the second and so on in a circle).
|
||||||
|
> - [**Weighted Round Robin**](). Improved algorithm Round Robin, which also takes into account the performance of the server.
|
||||||
|
> - [**Least Connections**](). Each subsequent request is sent to the server with the smallest number of supported connections.
|
||||||
|
> - **Destination Hash Scheduling**. The server that processes the request is selected from a static table based on the recipient's IP address.
|
||||||
|
> - **Source Hash Scheduling**. The server that will process the request is selected from the table by the sender's IP address.
|
||||||
|
> - [**Sticky Sessions**](). Requests are distributed based on the user's IP address. Sticky Sessions assumes that requests from the same client will be routed to the same server rather than bouncing around in a pool.
|
||||||
|
|
||||||
<details>
|
<details>
|
||||||
<summary>🔗 <b>References</b></summary>
|
<summary>🔗 <b>References</b></summary>
|
||||||
|
|
||||||
</details>
|
1. 📺 [**What is a Load Balancer?** – YouTube](https://youtu.be/sCR3SAVdyCc)
|
||||||
|
2. 📺 [**Learn Load Balancing right now** – YouTube](https://youtu.be/LlbTSfc4biw)
|
||||||
|
3. 📺 [**Load Balancing with NGINX** – YouTube](https://youtu.be/a41jxGP9Ic8)
|
||||||
|
4. 📺 [**Load Balancers id depth** – YouTube](https://youtu.be/galcDRNd5Ow)
|
||||||
|
</details>
|
||||||
|
|
||||||
<div align="right"><a href="#top">Contents ⬆️</a></div>
|
<div align="right"><a href="#top">Contents ⬆️</a></div>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user