зеркало из https://github.com/microsoft/msquic.git
b529c67796
For throughput tests, 43 is a magic number. Its 64,500 bytes, which is the largest UDP datagram able to be sent with a 1500 MTU. With a smaller batch size, we're not going to receive a full server send in 1 go, causing us to get behind. With a larger batch size, we can potentially grab a packet out of the next datagram send, causing send and receives to get out of sync with datagram boundaries. At 43, we pretty much run in lockstep, which results in the best performance RPS should not be affected, we're not increasing the value enough to cause over allocations. Also, each packet is its own allocation, so underused packets are just used again without freeing and reallocating |
||
|---|---|---|
| .azure | ||
| .github | ||
| cmake | ||
| docs | ||
| scripts | ||
| src | ||
| submodules | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| Dockerfile | ||
| LICENSE | ||
| README.md | ||
| THIRD-PARTY-NOTICES | ||
| msquic.kernel.sln | ||
README.md
MsQuic
MsQuic is a Microsoft implementation of the IETF QUIC protocol. It is cross platform, written in C and designed to be a general purpose QUIC library.
Important The QUIC protocol is not an official RFC yet. It has been approved by the IESG and now is in the RFC editor queue (final step).
IETF Drafts: Transport, TLS, Recovery, Datagram, Load Balancing, Version Negotiation
Protocol Features
QUIC has many benefits when compared to existing "TLS over TCP" scenarios:
- All packets are encrypted and handshake is authenticated with TLS 1.3.
- Parallel streams of (reliable and unreliable) application data.
- Exchange application data in the first round trip (0-RTT).
- Improved congestion control and loss recovery.
- Survives a change in the clients IP address or port.
- Stateless load balancing.
- Easily extendable for new features and extensions.
Library Features
MsQuic has several features that differentiates it from other QUIC implementations:
- Optimized for client and server.
- Optimized for maximal throughput and minimal latency.
- Asynchronous IO.
- Receive side scaling (RSS) support.
- UDP send and receive coalescing support.
Documentation
- For frequently asked questions, see the FAQs.
- For platform support details, see the Platforms docs.
- For release details, see the Release docs.
- For performance data, see the Performance dashboard.
- For building the MsQuic library, see the Build docs.
- For using the MsQuic API, see the API docs or the Sample.
- For deploying with MsQuic, see the Deployment docs.
- For diagnosing MsQuic, see the Diagnostics docs.
Contributing
For information on contributing, please see our contribution guidlines.