Libnodelay Alternatives

Similar projects and alternatives to libnodelay

go

2,066 119,397 10.0 Go libnodelay VS go

The Go programming language
kubernetes

656 106,611 10.0 Go libnodelay VS kubernetes

Production-Grade Container Scheduling and Management
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
.NET Runtime

605 14,047 10.0 C# libnodelay VS .NET Runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Caddy

401 53,568 9.4 Go libnodelay VS Caddy

Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
git-lfs

159 12,405 9.1 Go libnodelay VS git-lfs

Git extension for versioning large files
grpc-go

29 19,836 9.5 Go libnodelay VS grpc-go

The Go language implementation of gRPC. HTTP/2 based RPC
rke2

26 1,334 9.3 Go libnodelay VS rke2
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
plan9port

27 1,554 5.0 C libnodelay VS plan9port

Plan 9 from User Space
certificate-transparency-go

8 829 9.5 Go libnodelay VS certificate-transparency-go

Auditing for TLS certificates (Go code)
s2n

9 4,446 9.4 C libnodelay VS s2n

An implementation of the TLS/SSL protocols

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better libnodelay alternative or higher similarity.

Suggest an alternative to libnodelay

libnodelay reviews and mentions

Posts with mentions or reviews of libnodelay. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-29.

Golang is evil on shitty networks
21 projects | news.ycombinator.com | 29 Dec 2022

> not to mention nearly 50% of every packet was literally packet headers
I was just looking at a similar issue with grpc-go, where it would somehow send a HEADERS frame, a DATA frame, and a terminal HEADERS frame in 3 different packets. The grpc server is a golang binary (lightstep collector), which definitely disables Nagle's algorithm as shown by strace output, and the flag can't be flipped back via the LD_PRELOAD trick (e.g. with a flipped version of https://github.com/sschroe/libnodelay) as the binary is statically linked.
I can't reproduce this with a dummy grpc-go server, where all 3 frames would be sent in the same packet. So I can't blame Nagle's algorithm, but I am still not sure why the lightstep collector behaves differently.