avo
compress
avo | compress | |
---|---|---|
10 | 17 | |
2,598 | 4,506 | |
- | - | |
7.0 | 8.4 | |
about 1 month ago | 21 days ago | |
Go | Go | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
avo
-
From slow to SIMD: A Go optimization story
I wonder whether avo could have been useful here?[1] I mention it because it came up the last time we were talking about AVX operations in go.[2]
1 = https://github.com/mmcloughlin/avo
2 = https://news.ycombinator.com/item?id=34465297
- Portable Efficient Assembly Code-Generator in Higher-Level Python (PeachPy)
-
How to Use AVX512 in Golang
I thought the /r/golang comments on this post were pretty useful[1]. They also introduced me to avo[2], a tool for generating x86 assembly from go that I hadn't seen before. There are some examples listed on the avo github page for generating AVX512 instructions with avo.
1 = https://www.reddit.com/r/golang/comments/10hmh07/how_to_use_...
2 = https://github.com/mmcloughlin/avo
For writing AVX512 from scratch avo is a much better alternative.
-
SIMD Accelerated vector math
Avo is a library that simplifies writing complex go assembly, I found it very useful to figure out how instructions map onto Go's asm syntax. But you could definitely do the translation directly, it's what c2goasm did (couldn't get it to work reliably unfortunately).
-
HaxMap v0.2.0 released, huge performance improvements and added support for 32-bit systems
Curious if you're looking at using avo to write the assembly
-
HaxMap, a concurrent hashmap faster and more memory-efficient than golang's sync.Map
You can use github.com/mmcloughlin/avo for generating the assembly use Go.
-
S2: Fully Snappy compatible compression, faster and better
For normal and "better" mode I am using avo to generate different encoders for different input sizes, with and without Snappy compatibility. That currently outputs about 17k lines of assembly.
-
Branchless Coding in Go (Golang)
You could perhaps just have the Go compiler generate the assembler for your code:
go tool compile -S file.go > file_amd64.s
Then you could verify it doesn't change over time, and choose to begin maintaining by hand if it makes sense.
If you do want to go the route of rolling it yourself, I'd suggest looking into something like Avo: https://github.com/mmcloughlin/avo
-
High precision timer loop.
If you have to go with Assembly, try Avo https://github.com/mmcloughlin/avo
compress
- Chrome Feature: ZSTD Content-Encoding
-
Show HN: Gogosseract, a Go Lib for CGo-Free Tesseract OCR via Wazero
There's a pure-go zstd at https://github.com/klauspost/compress - it's likely faster than running the upstream zstd under Wazero.
-
When is go not a good choice?
It's no surprise that "fast" Go libraries are actually just assembly: https://github.com/klauspost/compress/blob/master/zstd/seqdec_amd64.s (just one file out of several, for just one architecture, for just one compression algorithm!)
-
zstd
There is a reasonably feature complete implementation of Zstd for Go: https://github.com/klauspost/compress/tree/master/zstd
It may not offer the same API 1:1, but it has no interoperability issues that I've encountered. So, I just think no one has bothered to implement it in Rust because most use cases don't mind the added bloat you're talking about. Plus, other comments I've seen suggest that you can actually tune the size of the zstd library, although I'm not sure if the Rust bindings expose that.
-
Medical image parser in Go
Thanks again for your review/comment!!! Btw, are you the author of this repo https://github.com/klauspost/compress because I love it!!!
-
Ask HN: Does https://github.com/klauspost/compress returns 502 for you?
I noticed Github returns "This page is taking too long to load" with status code 502 for https://github.com/klauspost/compress but rest of their urls works fine. Anyone know why would that be the case ?
Cloning the repo works perfectly well.
git clone https://github.com/klauspost/compress
- S2 Compression
-
Zstandard – Real-time data compression algorithm
Recent versions of zstd definitely don't obsolete LZ4, or else I don't think the author would still be contributing to both...
And if you're going to play with Snappy, you might find S2, which was linked on HN relatively recently, interesting. [1]
[1] - https://github.com/klauspost/compress/tree/master/s2
-
Restic 0.14.0 Released (with highly anticipated feature – compression)
Compression method appears to be zstandard and uses https://github.com/klauspost/compress, for those wondering like I was.
-
MinIO Object Placement Strategy in Distributed deployments
OMG u/klauspost is this you? https://github.com/klauspost/compress/tree/master/s2
What are some alternatives?
sonic - A blazingly fast JSON serializing & deserializing library
nodejs-js-compress-benchmark - Benchmark NodeJS/JS compression libraries
sha256-simd - Accelerate SHA256 computations in pure Go using AVX512, SHA Extensions for x86 and ARM64 for ARM. On AVX512 it provides an up to 8x improvement (over 3 GB/s per core). SHA Extensions give a performance boost of close to 4x over native.
go - The Go programming language
dingo - Generated dependency injection containers in go (golang)
sqlite-zstd - Transparent dictionary-based row-level compression for SQLite
rjson - A fast json parser for go
easyjson - Fast JSON serializer for golang.
gorse - Gorse open source recommender system engine
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
gzipped - Replacement for golang http.FileServer which supports precompressed static assets.