rust-cache
tokio
rust-cache | tokio | |
---|---|---|
6 | 196 | |
1,157 | 24,854 | |
- | 2.2% | |
7.3 | 9.5 | |
11 days ago | 6 days ago | |
TypeScript | Rust | |
GNU Lesser General Public License v3.0 only | MIT License |
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.
rust-cache
-
cargo cache in docker rust:latest
In Github Actions we use swatinem/rust-cache. They have a pretty good explanation of what they are doing, and if that's not enough you can have a look at what the code is doing
-
cargo-semver-checks v0.18.0: rustdoc caching, new lints & more
Out of curiosity, does this play well with the Swatinem/rust-cache action? To improve CI cache performance, it's good practice to cache only dependencies' artifacts, and this action as such automatically cleans out the workspace local artifacts before populating the cache.
-
actions-rs Github Actions need more maintainers!!! OR to be replaced
I've migrated to https://github.com/dtolnay/rust-toolchain for managing rustup, and https://github.com/Swatinem/rust-cache for caching
-
GitHub Actions best practices for Rust projects
I'd also like to drop a recommendation to use https://github.com/Swatinem/rust-cache for caching cargo-related artifacts. I found it to be extremely pleasant to use and very easy to integrate into my CI pipelines.
-
How should I go about making Rust workflows go faster with CI's with GitHub Actions? Are there any cache actions for Rust or a place I could look for general optimizations?
There is an awesome github actions plugin that configures caching for `~/.cargo` and `target/`: https://github.com/Swatinem/rust-cache
-
Looking for guidance/review on my first library: stroke-rs
Really cool! A few ideas: - cargo publish it! It'd be good to set the license, description, repository, and readme fields in Cargo.toml. - Your lib.rs looks good - clean & simply exporting types. - You could consider exporting Point/PointN at your library root (e.g. pub use them in lib.rs). If you expect a type will pretty much always be used, it's nice to export it at the root. It also makes those types easier to find on docs.rs. - There is a nifty github actions plugin that caches the crates.io registry, and your dependencies: https://github.com/Swatinem/rust-cache.
tokio
-
On Implementation of Distributed Protocols
Being able to control nondeterminism is particularly useful for testing and debugging. This allows creating reproducible test environments, as well as discrete-event simulation for faster-than-real-time simulation of time delays. For example, Cardano uses a simulation environment for the IO monad that closely follows core Haskell packages; Sui has a simulator based on madsim that provides an API-compatible replacement for the Tokio runtime and intercepts various POSIX API calls in order to enforce determinism. Both allow running the same code in production as in the simulator for testing.
-
I pre-released my project "json-responder" written in Rust
tokio / hyper / toml / serde / serde_json / json5 / console
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
tokio - An asynchronous runtime for Rust
-
Top 10 Rusty Repositories for you to start your Open Source Journey
3. Tokio
-
API Gateway, Lambda, DynamoDB and Rust
The AWS SDK makes use of the async capabilities in the Tokio library. So when you see async in front of a fn that function is capable of executing asynchronously.
-
The More You Gno: Gno.land Monthly Updates - 6
Petar is also looking at implementing concurrency the way it is in Go to have a fully functional virtual machine as it is in the spec. This would likely attract more external contributors to developing the VM. One advantage of Rust is that, with the concurrency model, there is already an extensive library called Tokio which he can use. Petar stresses that this isnโt easy, but he believes itโs achievable, at least as a research topic around determinism and concurrency.
-
Consuming an SQS Event with Lambda and Rust
Another thing to point out is that async is a thing in Rust. I'm not going to begin to dive into this paradigm in this article, but know it's handled by the awesome Tokio framework.
-
netcrab: a networking tool
So I started by using Tokio, a popular async runtime. The docs and samples helped me get a simple outbound TCP connection working. The Rust async book also had a lot of good explanations, both practical and digging into the details of what a runtime does.
-
Thread-per-Core
Regarding the quote:
> The Original Sin of Rust async programming is making it multi-threaded by default. If premature optimization is the root of all evil, this is the mother of all premature optimizations, and it curses all your code with the unholy Send + 'static, or worse yet Send + Sync + 'static, which just kills all the joy of actually writing Rust.
Agree about the melodramatic tone. I also don't think removing the Send + Sync really makes that big a difference. It's the 'static that bothers me the most. I want scoped concurrency. Something like <https://github.com/tokio-rs/tokio/issues/2596>.
Another thing I really hate about Rust async right now is the poor instrumentation. I'm having a production problem at work right now in which some tasks just get stuck. I wish I could do the equivalent of `gdb; thread apply all bt`. Looking forward to <https://github.com/tokio-rs/tokio/issues/5638> landing at least. It exists right now but is experimental and in my experience sometimes panics. I'm actually writing a PR today to at least use the experimental version on SIGTERM to see what's going on, on the theory that if it crashes oh well, we're shutting down anyway.
Neither of these complaints would be addressed by taking away work stealing. In fact, I could keep doing down my list, and taking away work stealing wouldn't really help with much of anything.
-
PHP-Tokio โ Use any async Rust library from PHP
The PHP <-> Rust bindings are provided by https://github.com/Nicelocal/ext-php-rs/ (our fork of https://github.com/davidcole1340/ext-php-rs with a bunch of UX improvements :).
php-tokio's integrates the https://revolt.run event loop with the https://tokio.rs event loop; async functionality is provided by the two event loops, in combination with PHP fibers through revolt's suspension API (I could've directly used the PHP Fiber API to provide coroutine suspension, but it was a tad easier with revolt's suspension API (https://revolt.run/fibers), since it also handles the base case of suspension in the main fiber).
What are some alternatives?
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
async-std - Async version of the Rust standard library
bors-ng - ๐ A merge bot for GitHub Pull Requests
Rocket - A web framework for Rust.
toolchain - ๐ ๏ธ GitHub Action for `rustup` commands
hyper - An HTTP library for Rust
rust-toolchain - Concise GitHub Action for installing a Rust toolchain
futures-rs - Zero-cost asynchronous programming in Rust
audit-check - ๐ก๏ธ GitHub Action for security audits
smol - A small and fast async runtime for Rust
cargo-deny-action - โ GitHub Action for cargo-deny ๐ฆ
rayon - Rayon: A data parallelism library for Rust