hyperfine
quinn
Our great sponsors
hyperfine | quinn | |
---|---|---|
74 | 23 | |
19,874 | 3,449 | |
- | 2.7% | |
8.2 | 9.0 | |
12 days ago | about 18 hours ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hyperfine
-
Measuring startup and shutdown overhead of several code interpreters
Check out the official hyperfine Github repo
-
Bun - The One Tool for All Your JavaScript/Typescript Project's Needs?
And then I used hyperfine to run the benchmarks on my MacBook Pro 14 M2 Max, and here are the results:
-
Faster tetranucleotide (k-mer) frequencies!
Search "benchmarking tools for linux" and decide that hyperfine is good for what I'm doing. Run Jennifer's new python script against my refactored perl and find that the python is 1.26 times faster for k=3 and 1.47 times faster for k=4. For the Covid-19 sequence, these are both on the order of hundreds of milliseconds.
- Hyperfine: A command-line benchmarking tool
- FLaNK Weekly 08 Jan 2024
-
Show HN: Inshellisense – IDE style shell autocomplete
> It is very possible to write sub 100ms procedures in TS, […]
I will not disagree with this statement because I don’t have a way to test inshellisense right now. Could you (or anyone with a working Node + NPM installation) please install inshellisense and post the actual numbers? Perhaps using a tool like hyperfine (https://github.com/sharkdp/hyperfine).
-
Firefox has surpassed Chrome on Speedometer
Yeah, while it's not as thorough as these tools, the method is at least reproducible and sane, and with ~10 or so samples, you get an interval with a nice confidence.
Another through method will be hyperfine[0], yet I wanted to provide a method which requires no installation and can be done in a whim, without jumps and hoops, with the tools already at hand.
-
How to optimize your config? What are mistakes to avoid when optimizing your config?
That is native and inbuild but I would suggest below options instead 1. Using lazy's Profile tab instead https://github.com/folke/lazy.nvim 2. Using a dedicated plugin to do this https://github.com/dstein64/vim-startuptime. 3. Using an external program hyperfine is one that I use https://github.com/sharkdp/hyperfine
-
How to remove all <br> from all of my .html files
Fair enough, although might I recommend using hyperfine for your testing? ;p
quinn
-
Why HTTP/3 is eating the world
Since it lives on top of UDP, I believe all you need is SOCK_DGRAM, right? The rest of QUIC can be in a userspace library ergonomically designed for your programming language e.g. https://github.com/quinn-rs/quinn - and can interoperate with others who have made different choices.
Alternately, if you need even higher performance, DPDK gives the abstractions you'd need; see e.g. https://dl.acm.org/doi/abs/10.1145/3565477.3569154 on performance characteristics.
-
Async rust – are we doing it all wrong?
> Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing what I'm doing in my code above would be to spawn one of the loops on a separate background task, which could land on a separate thread, meaning we must do all that synchronization to manage reading and writing to a socket from different threads for no good reason.
Why so? Libraries like quinn[1] define "no IO" crate to define runtime-agnostic protocol implementation. In this way we won't suffer by forcing ourselves using synchronization primitives.
Also, IMO it's relatively easy to use Send-bounded future in non-Send(i.o.w. single-threaded) runtime environment, but it's almost impossible to do opposite. Ecosystem users can freely use single threaded async runtime, but ecosystem providers should not. If you want every users to only use single threaded runtime, it's a major loss for the Rust ecosystem.
Typechecked Send/Sync bounds are one of the holy grails that Rust provides. Albeit it's overkill to use multithreaded async runtimes for most users, we should not abandon them because it opens an opportunity for high-end users who might seek Rust for their high-performance backends.
-
quicssh-rs Rust implementation SSH over Quic proxy tool
quicssh-rs is quicssh rust implementation. It is based on quinn and tokio
-
The birth of a package manager [written in Rust :)]
Regarding Quinn, I had a blast this week resurrecting an old PR. Looking forward to the next!
- Best performing quic implementation?
-
str0m a sans I/O WebRTC library
By studying u/djcu/hachyderm.io (and others!) excellent work in Quinn, doing a sans I/O implementation of QUIC https://github.com/quinn-rs/quinn we have a way forward.
-
durian - a high-level general purpose client/server networking library
QUIC isn't web/wasm-compatible because of https://github.com/quinn-rs/quinn/issues/1388, so durian wouldn't either since it's built on top of it.
-
FPS server with QUINN?
Quinn, as in the implementation of QUIC? https://github.com/quinn-rs/quinn
-
I built a Zoom clone 100% IN RUST
You are right, I am planning to switch the transport to UDP + quic using the awesome QUINN library, https://github.com/quinn-rs/quinn .
-
I write a secure UDP tunnel
Hi, I am new to the community, I just started learning rust and created a secure UDP tunnel based on the Quinn library, thanks to Quinn, I didn't need to go into the detail of the QUIC protocol and quickly created a UDP tunnel, and thanks to the BBR congestion control algorithm it uses, the tunnel performs quite well with lousy and long fat network, I didn't do any benchmark, but it performs a lot better (higher throughput with LFN) than most of other TCP tunnel implementations I used before.
What are some alternatives?
criterion.rs - Statistics-driven benchmarking library for Rust
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
fd - A simple, fast and user-friendly alternative to 'find'
s2n-quic - An implementation of the IETF QUIC protocol
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
h3
awesome-mac - Now we have become very big, Different from the original idea. Collect premium software in various categories.
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
kubeconform - A FAST Kubernetes manifests validator, with support for Custom Resources!
laminar - A simple semi-reliable UDP protocol for multiplayer games
neqo - Neqo, an implementation of QUIC in Rust