mirror of
https://github.com/gofiber/fiber.git
synced 2025-05-15 12:10:29 +00:00
71 lines
2.8 KiB
Markdown
71 lines
2.8 KiB
Markdown
---
|
|
id: benchmarks
|
|
title: 📊 Benchmarks
|
|
description: >-
|
|
These benchmarks aim to compare the performance of Fiber and other web
|
|
frameworks.
|
|
sidebar_position: 2
|
|
---
|
|
|
|
## TechEmpower
|
|
|
|
[TechEmpower](https://www.techempower.com/benchmarks/#section=data-r23) provides a performance comparison of many web application frameworks executing fundamental tasks such as JSON serialization, database access, and server-side template composition.
|
|
|
|
Each framework is operating in a realistic production configuration. Results are captured on cloud instances and on physical hardware. The test implementations are largely community-contributed and all source is available at the [GitHub repository](https://github.com/TechEmpower/FrameworkBenchmarks).
|
|
|
|
* Fiber `v2.52.5`
|
|
* 56 Cores Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz (Three homogeneous ProLiant DL360 Gen10 Plus)
|
|
* 64GB RAM
|
|
* Enterprise SSD
|
|
* Ubuntu
|
|
* Mellanox Technologies MT28908 Family ConnectX-6 40Gbps Ethernet
|
|
|
|
### Plaintext
|
|
|
|
The Plaintext test is an exercise of the request-routing fundamentals only, designed to demonstrate the capacity of high-performance platforms in particular. Requests will be sent using HTTP pipelining. The response payload is still small, meaning good performance is still necessary in order to saturate the gigabit Ethernet of the test environment.
|
|
|
|
See [Plaintext requirements](https://github.com/TechEmpower/FrameworkBenchmarks/wiki/Project-Information-Framework-Tests-Overview#single-database-query)
|
|
|
|
**Fiber** - **13,509,592** responses per second with an average latency of **0.9** ms.
|
|
**Express** - **279,922** responses per second with an average latency of **551.3** ms.
|
|
|
|
|
|
|
|
|
|
|
|
### Data Updates
|
|
|
|
**Fiber** handled **30,884** responses per second with an average latency of **16.5** ms.
|
|
**Express** handled **50,818** responses per second with an average latency of **10.1** ms.
|
|
|
|
|
|
|
|
|
|
|
|
### Multiple Queries
|
|
|
|
**Fiber** handled **55,577** responses per second with an average latency of **9.2** ms.
|
|
**Express** handled **62,036** responses per second with an average latency of **8.3** ms.
|
|
|
|
|
|
|
|
|
|
|
|
### Single Query
|
|
|
|
**Fiber** handled **1,000,519** responses per second with an average latency of **0.5** ms.
|
|
**Express** handled **214,177** responses per second with an average latency of **2.5** ms.
|
|
|
|
|
|
|
|
|
|
|
|
### JSON Serialization
|
|
|
|
**Fiber** handled **2,479,768** responses per second with an average latency of **0.2** ms.
|
|
**Express** handled **301,213** responses per second with an average latency of **2.0** ms.
|
|
|
|
|
|
|
|
|