typedload
simdjson-go
typedload | simdjson-go | |
---|---|---|
5 | 6 | |
254 | 1,761 | |
- | 0.5% | |
8.1 | 4.0 | |
7 days ago | 6 months ago | |
Python | Go | |
GNU General Public License v3.0 or later | 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.
typedload
-
Show HN: Up to 100x Faster FastAPI with simdjson and io_uring on Linux 5.19
Author of typedload here!
FastAPI relies on (not so fast) pydantic, which is one of the slowest libraries in that category.
Don't expect to find such benchmarks on the pydantic documentation itself, but the competing libraries will have them.
[0] https://ltworf.github.io/typedload/
-
Pydantic vs Protobuf vs Namedtuples vs Dataclasses
I wrote typedload, which is significantly faster than pydantic. Just uses normal dataclasses/attrs/NamedTuple, has a better API and is pure Python!
- Informatica serve a qualcosa?
-
Show HN: Python framework is faster than Golang Fiber
I read all the perftests in the repo. I think they nearly all parse a structure that contains a repetition of the same or similar thing a couple hundred thousand times times and the timing function returns the min and max of 5 attempts. I just picked one example for posting.
Not a Python expert, but could the Pydantic tests be possibly not realistic and/or misleading because they are using kwargs in __init__ [1] to parse the object instead of calling the parse_obj class method [2]? According to some PEPs [3], isn't Python creating a new dictionary for that parameter which would be included in the timing? That would be unfortunate if that accounted for the difference.
Something else I think about is if a performance test doesn't produce a side effect that is checked, a smart compiler or runtime could optimize the whole benchmark away. Or too easy for the CPU to do branch prediction, etc. I think I recall that happening to me in Java in the past, but probably not happened here in Python.
[1] https://github.com/ltworf/typedload/blob/37c72837e0a8fd5f350...
[2] https://docs.pydantic.dev/usage/models/#helper-functions
[3] https://peps.python.org/pep-0692/
simdjson-go
-
Show HN: Up to 100x Faster FastAPI with simdjson and io_uring on Linux 5.19
Speaking of Go, there's a simdjson implementation for golang too:
> Performance wise, simdjson-go runs on average at about 40% to 60% of the speed of simdjson. Compared to Golang's standard package encoding/json, simdjson-go is about 10x faster.
I haven't tried it yet but I don't really need that speed.
https://github.com/minio/simdjson-go
-
How to Use AVX512 in Golang
I agree. For performance-sensitive situations, C/C++ or Rust is the only choice. However, many developers choose Go or other languages for engineering efficiency. A typical use case of SIMD in Go is simdjson-go. Besides, there are plenty of bindings and ports of simdjson. "Other languages" developers also need performance improvement from native instructions such as SIMD.
- Sonic: A fast JSON serializing and deserializing library
- Whats the fastest JSON unmarshaling package as of right now?
-
What is the best solution to unique data in golang
I suggest to use a streaming library to parse your file. Like jstream or simdjson-go
-
I wrote yet another json parser. It may be a contender for fastest.
You can also try comparing with https://github.com/minio/simdjson-go. It does use a different API, however, would be good to compare nevertheless.
What are some alternatives?
codon - A high-performance, zero-overhead, extensible Python compiler using LLVM
easyjson - Fast JSON serializer for golang.
ustore - Multi-Modal Database replacing MongoDB, Neo4J, and Elastic with 1 faster ACID solution, with NetworkX and Pandas interfaces, and bindings for C 99, C++ 17, Python 3, Java, GoLang 🗄️
jstream - Streaming JSON parser for Go
pydantic-core - Core validation logic for pydantic written in rust
jsonparser - One of the fastest alternative JSON parser for Go that does not require schema
peps - Python Enhancement Proposals
sonic - A blazingly fast JSON serializing & deserializing library
msgspec - A fast serialization and validation library, with builtin support for JSON, MessagePack, YAML, and TOML
jsonlite - A simple, self-contained, serverless, zero-configuration, json document store.
koda-validate - Typesafe, Composable Validation
rjson - A fast json parser for go