VK-GL-CTS
simdjson
Our great sponsors
VK-GL-CTS | simdjson | |
---|---|---|
17 | 65 | |
496 | 18,362 | |
1.0% | 1.2% | |
9.9 | 9.2 | |
9 days ago | 19 days ago | |
C++ | C++ | |
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.
VK-GL-CTS
- What coin will pump in 2023?
-
A770/A750 Performance in Minecraft Java?
Minecraft Java edition uses the OpenGL graphics engine, which was created by the Khronos Group. Vulkan was also created by them.
-
I have a problemo
In the C++ standard, there is nothing. But if you are searching for something that can qualify as a standard, try the Khronos Group libs, here: https://www.khronos.org/
- Performance of GL_POINTS vs compute shader for 1x1 quads
-
How the SYCL spec gets updated
The caretaker of the SYCL spec is Khronos a non-profit standards body that is home to several projects focused on graphics, machine learning, parallel computing, VR and visual computing. You will note that all these pieces work together to build frameworks. Some of the more visible ones that you might be familiar with are openGL and Vulkan.
-
Discussion Thread
Why does the Khronos group have so many standards? Do they really need all this?
-
Linux M1 GPU driver passes 99% of the dEQP-GLES2 compliance tests
It's more than that, it's the official conformance tests:
https://github.com/KhronosGroup/VK-GL-CTS/blob/main/external...
-
Compressed Texture Converter/Writer
https://www.khronos.org/ is the open standards body in charge of OpenGL and Vulkan. They’re pretty far from being a big commercial product maker ;)
-
Haptics Industry Forum and Khronos forge cooperative liaison to bring haptics to the Metaverse
The Haptics Industry Forum (HIF) and The Khronos® Group have entered into a cooperative liaison agreement to foster synergy between the two organizations to encourage the integration of advanced haptics functionality into the Khronos OpenXR™ open standard for portable augmented and virtual reality, to enable broad availability of haptics in the metaverse and beyond. This agreement enables HIF and Khronos to collaborate with a shared goal to enable broad, cross-platform access to next-generation haptic feedback in XR applications, enabling rich multisensory experiences to reach beyond 3D visuals for the eyes and spatial audio for the ears – and include expressive haptics for touch.
-
Metaverse app allows kids into virtual strip clubs
The true metaverse concept (not rebranded private apps like roblox, vrchat, second life, decentraland or horizons) will be based on an open set of standards, which are still in development.
simdjson
-
Tips on adding JSON output to your command line utility. (2021)
It's also supported by simdjson [0] (which has a lot of language bindings [1]):
> Multithreaded processing of gigantic Newline-Delimited JSON (ndjson) and related formats at 3.5 GB/s
[0] https://simdjson.org/
[0] https://github.com/simdjson/simdjson?tab=readme-ov-file#bind...
- 1BRC Merykitty's Magic SWAR: 8 Lines of Code Explained in 3k Words
- Training great LLMs from ground zero in the wilderness as a startup
- simdjson: Parsing Gigabytes of JSON per Second
-
Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
String parsing is negligible compared to the speed of the DOM which is glacially slow: https://news.ycombinator.com/item?id=38835920
Come on, people, make an effort to learn how insanely fast computers are, and how insanely inefficient our software is.
String parsing can be done at gigabytes per second: https://github.com/simdjson/simdjson If you think that is the slowest operation in the browser, please find some resources that talk about what is actually happening in the browser?
-
Cray-1 performance vs. modern CPUs
Thanks for all the detailed information! That answers a bunch of my questions and the implementation of strlen is nice.
The instruction I was thinking of is pshufb. An example ‘weird’ use can be found for detecting white space in simdjson: https://github.com/simdjson/simdjson/blob/24b44309fb52c3e2c5...
This works as follows:
1. Observe that each ascii whitespace character ends with a different nibble.
2. Make some vector of 16 bytes which has the white space character whose final nibble is the index of the byte, or some other character with a different final nibble from the byte (eg first element is space =0x20, next could be eg 0xff but not 0xf1 as that ends in the same nibble as index)
3. For each block where you want to find white space, compute pcmpeqb(pshufb(whitespace, input), input). The rules of pshufb mean (a) non-ascii (ie bit 7 set) characters go to 0 so will compare false, (b) other characters are replaced with an element of whitespace according to their last nibble so will compare equal only if they are that whitespace character.
I’m not sure how easy it would be to do such tricks with vgather.vv. In particular, the length of the input doesn’t matter (could be longer) but the length of white space must be 16 bytes. I’m not sure how the whole vlen stuff interacts with tricks like this where you (a) require certain fixed lengths and (b) may have different lengths for tables and input vectors. (and indeed there might just be better ways, eg you could imagine an operation with a 256-bit register where you permute some vector of bytes by sign-extending the nth bit of the 256-bit register into the result where the input byte is n).
-
Codebases to read
Additionally, if you like low level stuff, check out libfmt (https://github.com/fmtlib/fmt) - not a big project, not difficult to understand. Or something like simdjson (https://github.com/simdjson/simdjson).
- Simdjson: Parsing Gigabytes of JSON per Second
-
Building a high performance JSON parser
Everything you said is totally reasonable. I'm a big fan of napkin math and theoretical upper bounds on performance.
simdjson (https://github.com/simdjson/simdjson) claims to fully parse JSON on the order of 3 GB/sec. Which is faster than OP's Go whitespace parsing! These tests are running on different hardware so it's not apples-to-apples.
The phrase "cannot go faster than this" is just begging for a "well ackshully". Which I hate to do. But the fact that there is an existence proof of Problem A running faster in C++ SIMD than OP's Probably B scalar Go is quite interesting and worth calling out imho. But I admit it doesn't change the rest of the post.
-
New package : lspce - a simple LSP Client for Emacs
I have same question as /u/JDRiverRun : how do you deal with JSON, do you parse json on Rust side or on Emacs side. I see that you are requiring json.el in your lspce.el, but I haven't looked through entire file carefully. If you parse on Rust side, do you use simdjson (there are at least two Rust bindings to it)? If yes, what are your impressions, experiences compared to more "standard" json library?
What are some alternatives?
apitrace - Tools for tracing OpenGL, Direct3D, and other graphics APIs
RapidJSON - A fast JSON parser/generator for C++ with both SAX/DOM style API
magnum-examples - Examples for the Magnum C++11 graphics engine
jsoniter - jsoniter (json-iterator) is fast and flexible JSON parser available in Java and Go
basis_universal - Basis Universal GPU Texture Codec
json - JSON for Modern C++
filament - Filament is a real-time physically based rendering engine for Android, iOS, Windows, Linux, macOS, and WebGL2
json-schema-validator - JSON schema validator for JSON for Modern C++
vulkan_renderer - A toy renderer written in C using Vulkan to perform real-time ray tracing research.
JsonCpp - A C++ library for interacting with JSON.
Mapbox GL - Interactive, thoroughly customizable maps in native Android, iOS, macOS, Node.js, and Qt applications, powered by vector tiles and OpenGL
json - A C++11 library for parsing and serializing JSON to and from a DOM container in memory.