raspberry-pi-pcie-devices VS simdjson

Are you familiar with a YouTuber named Jeff Geerling? He does some pretty far out stuff with pi’s like connecting video cards to them, etc. here’s a videoabout stuff you could do, I haven’t watched it myself. He’s got this website that has a list of accessories he’s tried with the pi. While I was looking for his channel I saw a ton of videos on YouTube for stuff to do with the pi. Curious to see what you end up doing… I guess I’m kinda hoping you do something that utilizes the full potential of the 4 😁

If you want to use SAS with the Pi, I've only gotten newer generation Broadcom/LSI cards working so far—see my notes for the storage controllers here: https://pipci.jeffgeerling.com/#sata-cards-and-storage

There's also a GitHub issue with a ton more detail about the chips used, and usage notes from a few different people.

Still working on that... https://pipci.jeffgeerling.com/#gpus-graphics-cards

I'm thinking of using the Waveshare for USB3 but maybe someone can suggest something for that PCI slot? Should I just grab a basic adapter? I like something like that HLT one but would want USB3 on the other end with a mountable input. I was also looking to go to the HiFiBerry DAC2 Pro for exposure to the GPIO.

And you can follow along with some tests here: https://github.com/geerlingguy/raspberry-pi-pcie-devices/issues/64

Note that different network chips can get different amounts of performance through the Pi's bus. An ASUS 10G card can get 2.99 Gbps with standard 1500 MTU, or 3.26 Gbps at 9000 MTU (see https://github.com/geerlingguy/raspberry-pi-pcie-devices/issues/15#issuecomment-752200920).

Check out the linked GitHub repo: https://pipci.jeffgeerling.com/ — for any card I'm actually testing, I have an open issue. For proposals or discussions around a certain topic, there are some ongoing conversations in the Discussions tab.

Specifically concerning Infiniband, check out this issue: https://github.com/geerlingguy/raspberry-pi-pcie-devices/dis... - I'd be willing to test, but currently I have a bit of a backlog of other gear I'm getting through testing :)

Follow https://github.com/geerlingguy/raspberry-pi-pcie-devices/iss... for progress. You can't boot directly from the SSD without a microSD card, but it (or SATA support for boot) may come soon... just a question of priorities for the Pi Engineering team.

There are a few addon boards (for $15-30, most shipping after the new year) that take the CM4 that extra mile: https://github.com/geerlingguy/raspberry-pi-pcie-devices/iss...

I'm most excited about a few with mini PCIe or M.2 slots on the bottom.

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?

I expect a lot of transcoders will be rewritten when the Vector instructions land. You can see speedups when used in other languages, such as simdjson. Please try to be more thoughtful and not disregard other people's hard work so easily.

You will never make 150GB/s though. Not even close. For example, simdjson achieves 3GB/s and is by far the fastest JSON parser out there.

Would you consider SIMD operations parallel? https://github.com/simdjson/simdjson

I'm talking about with simdjson. Lemire suggested reading line-by-line is not a good idea [0]. So I'm asking about the ideal approach using simdjson, not JSON parsers in general.

[0] https://github.com/simdjson/simdjson/issues/188#issuecomment...

Hey folks, if you've been in IRC this last week you've probably heard me mumbling to myself, or crying out in agony trying to bind Raku to simdjson. However, the pain was not in vain!

It’s a Swift wrapper around simdjson and a drop-in replacement for JSONDecoder. The performance should be pretty good.

One could combine JSON and a serializationless library, your JSON would be blown up with whitespace, but read and update could be O(1), serialization would be a memcpy, you could probably canonicalize the json during the memcpy using the SIMD techniques of Lemire.

I did this one for reading json on the fast path, the sending system laid out the arrays in a periodic pattern in memory that enabled parseless retrieval of individual values.

https://github.com/simdjson/simdjson

JSON can be parsed very quickly: https://github.com/simdjson/simdjson

CBOR could be another option: https://en.wikipedia.org/wiki/CBOR