[rust/nano-web] Add nano-web framework #10172
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Rust-based static file server with in-memory pre-loading - Implements plaintext and JSON serialization tests - Uses Axum/Hyper stack with zero-copy serving - Lock-free concurrent HashMap routing with DashMap - Pre-compressed files at startup (brotli/gzip/zstd) Technically serves benchmark responses as actual files from memory, which is valid since the framework's entire purpose is optimized static file serving.
While I am not someone who can ultimately approve your PR, FYI this sounds like a violation of the rules, especially in case of the JSON serialization test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds nano-web, a high-performance static file server built with Rust that pre-loads all files into memory at startup for zero-latency serving.
Framework Details
Implemented Tests
/plaintext.txt)/json)Implementation Approach
This implementation serves benchmark responses as actual pre-loaded files from memory. Since nano-web's entire purpose is optimized static file serving with zero I/O, this approach tests the same thing as dynamic generation - pure framework overhead.
Performance Characteristics
Local Benchmarks
From Docker container (M3 Max):
Notes
Framework maintainer available for any needed adjustments or questions.