I maintain cuTile Rust and just posted the paper "Fearless Concurrency on the GPU." As more GPU code gets AI-generated, the bottleneck moves from writing it to trusting it. cuTile Rust lets you write or generate GPU kernels whose memory safety and data-race freedom are verified by the compiler, through Rust's ownership and borrow checking. You get those guarantees by construction. It's a tile-based programming model that lowers to CUDA Tile IR, carrying Rust's ownership model across the launch boundary. You partition a mutable output into disjoint mutable sub-tensors, pass inputs as shared references, and write tile kernels with single-threaded semantics that the compiler maps to thread blocks. End to end, we built Grout, a Qwen3 inference engine, on cuTile Rust with Hugging Face. At batch-1 decode it reaches 171 tok/s for Qwen3-4B on an RTX 5090 and 82 tok/s for Qwen3-32B on a B200, competitive with vLLM and SGLang. Batch-1 decode is memory-bandwidth-bound, and Grout's throughput is consistent with our HBM roofline analysis. Many of Grout's kernels still use the unsafe path today, but they can be migrated to safe variants, providing a verifiable target for generated kernels. We've started a collection of such kernels in the cutile-kernels crate in the repo. If this is your thing, contributing safe variants helps grow a library of safe, high-performance kernels that future kernel synthesis can draw from. On the kernel side, the safety is effectively free. On a B200 the safe GEMM is within 0.3% of a hand-written low-level version (~92% of dense f16 peak), and element-wise hits ~7 TB/s, matching cuTile Python within measurement noise. Some additional caveats worth noting: Grout is batch-1 with a small set of supported models (a research case study, not a drop-in server), it's NVIDIA-only (lowers to Tile IR), and GEMM still slightly trails cuBLAS at some sizes. - Paper: https://arxiv.org/abs/2606.15991 - Code: https://github.com/nvlabs/cutile-rs - Grout: https://github.com/huggingface/grout Hope you enjoy the paper and learn something new! Happy to answer any questions :) submitted by /u/Exciting_Suspect9088 [link] [Kommentare]
Anyone else furious about Kraken still holding our Humanity Protocol ($H) tokens hostage? Every other major exchange—Binance, Bybit, KuCoin, Gate—already processed the 1:1 token migration and reinstated trading days ago. Meanwhile, Kraken is sitting on their hands, completely stripping away our right to manage our own risk. Their "we're protecting retail" narrative is complete garbage when the house is actively burning down and we aren't even allowed to run for the exit. At this point, it feels like they are intentionally dragging their feet to wait out the massive token unlock scheduled for next week. If they keep trading frozen until those millions of tokens flood the market and obliterate the price even further, Kraken users are the only ones getting completely left behind without a single chance to salvage their capital. Kraken Support, stop the corporate stalling and give us an actual timeline. Let us trade or transfer our assets. Taking away the sell button isn't protection—it's negligence. submitted by /u/tallcantommy23 [link] [Kommentare]
Diskless Kafka® on S3. 10x Cost-Effective. No Cross-AZ Traffic Cost. Autoscale in seconds. Single-digit ms latency. Multi-AZ Availability. - AutoMQ/automq
The standard definition of done stops at shipped code. Real done is when the customer’s problem is solved, and AI just made that the only one that matters.
I swear there's never been a single positive news story on crypto, even the attorneys are mocking it. submitted by /u/MW2_Lobbies [link] [Kommentare]
Why WER/CER misjudge Indian-language ASR when scripts mix and spellings vary. Covers LLM-WER, LLM-CER, Intent, Entity, and COMET-plus open evaluation tooling.