Search Results for "memory usage"

Pingora is a Rust-based high-performance HTTP proxy and networking framework developed by Cloudflare to eventually replace NGINX. Designed for extreme reliability and memory-safe concurrency, it handles over 40 million requests per second in production and reduces CPU/memory usage significantly compared to traditional web servers.

Lua HTTP client cosocket driver for OpenResty / ngx_lua. HTTP 1.0 and 1.1 SSL. Streaming interface to the response body, for predictable memory usage. Alternative simple interface for single-shot requests without a manual connection step. Chunked and non-chunked transfer encodings. Connection keepalives. Request pipelining. Trailers, HTTP proxy connections, and mTLS.

...Its API simplifies standards-compliant HTTP resource traversal and RESTful web service consumption without obscuring the underlying protocol. The library manually implements HTTP over TCP sockets; as such it has no dependency on ext/curl. Streams entity bodies for memory management with large transfers. Supports all standard and custom HTTP method verbs. Simplifies HTTP form submissions. Implements secure-by-default TLS. Supports cookies and sessions. Functions seamlessly behind HTTP proxies. Additionally, you might want to install the nghttp2 library to take advantage of FFI to speed up and reduce the memory usage on PHP 7.4. ...

LaravelS is an out-of-the-box adapter between Laravel/Lumen and Swoole. LaravelS uses Swoole's Synchronous IO mode, the larger the worker_num setting, the better the concurrency performance, but it will cause more memory usage and process switching overhead. If one request takes 100ms, in order to provide 1000QPS concurrency, at least 100 Worker processes need to be configured. Create WebSocket Handler class, and implement interface WebSocketHandlerInterface. The instant is automatically instantiated when start, you do not need to manually create it.

...It comfortably handles tens of thousands of requests/sec on even midrange hardware. Here is another test about how it stacks up with others. It's not only fast, but efficient! Each connection costs nothing but a few kB of memory. RAM usage grows O(n) with connections. Written from the ground-up to be lean, the entire client/server is available as a single ~90kB JAR with zero dependencies and ~3k lines of (mostly Java) code. Synchronous is simple. Asynchronous is fast & flexible.

...It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink. aria2 can be manipulated via built-in JSON-RPC and XML-RPC interfaces. aria2 can download a file from multiple sources/protocols and tries to utilize your maximum download bandwidth. Really speeds up your download experience. aria2 doesn’t require much memory and CPU time. When disk cache is off, the physical memory usage is typically 4MiB (normal HTTP/FTP downloads) to 9MiB (BitTorrent downloads). CPU usage in BitTorrent with a download speed of 2.8MiB/sec is around 6%. aria2 supports The Metalink Download Description Format (aka Metalink v4), Metalink version 3, and Metalink/HTTP. Metalink offers the file verification, HTTP/FTP/SFTP/BitTorrent integration and various configurations for language, location, OS, etc.

mango is a free, open source, lightweight HTTP Client library written entirely in C. The focus of the mango implementation is to reduce resource usage while still providing an almost full-scale HTTP Client. This makes it suitable for use in memory-constrained embedded devices where memory and CPU power are at a premium.