Impressive. I'm sure the numbers will continue to improve as both the FFM and this project mature.
Java Native databases or KVP stores would be good usage targets IMHO
Java FFM zero-copy transport using io_uring
41–50 of 59 posts
Re: Java FFM zero-copy transport using io_uring
#42Earlier quoted context omitted.
I just wrote in details on the same in a reply to nateb2022. https://news.ycombinator.com/item?id=46257205
I don't see a reply to nateb2022 by you.
Turn on showdead. Newly created accounts are more likely to have their first few postings [dead] because of rampant abuse.
Re: Java FFM zero-copy transport using io_uring
#43Earlier quoted context omitted.
Asking for those who, like me, haven't yet taken the time to find technical information on that webpage: What exactly does that roundtrip latency number measure (especially your 1us)? Does zero copy imply mapping pages between processes? Is there an async kernel component involved (like I would infer from "io_uring") or just two user space processes mapping pages?
27us and 1us are both an eternity and definitely not SOTA for IPC. The fastest possible way to do IPC is with a shared memory resident SPSC queue. The actual (one-way cross-core) latency on modern CPUs varies by quite a lot [0], but a good rule of thumb is 100ns + 0.1ns per byte. This measures the time for core A to write one or more cache lines to a shared memory region, and core B to read them. The latency is deter…
I was really asking what "IPC" means in this context. If you can just share a mapping, yes it's going to be quite fast. If you need to wait for approval to come back, it's going to take more time. If you can't share a memory segment, even more time.
Re: Java FFM zero-copy transport using io_uring
#44This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
Apologies! It's a long read and was the only time I did not want to use AI to summarize for a purpose :) ---- So Yes, a lot of the code has been written using AI. I have also been transparent about it on https://www.mvp.express/philosophy/ in the section "AI-Assisted Development". However, that does not mean that I as the author do not understand the code/concepts :) I also don't deny the fact that I might not have g…
> However, that does not mean that I as the author do not understand the code/concepts :) I also don't deny the fact that I might not have gone through the entire codebase till now.
You didn't go through the codebase, but you understand the code? What?
Re: Java FFM zero-copy transport using io_uring
#45Earlier quoted context omitted.
27us and 1us are both an eternity and definitely not SOTA for IPC. The fastest possible way to do IPC is with a shared memory resident SPSC queue. The actual (one-way cross-core) latency on modern CPUs varies by quite a lot [0], but a good rule of thumb is 100ns + 0.1ns per byte. This measures the time for core A to write one or more cache lines to a shared memory region, and core B to read them. The latency is deter…
I was really asking what "IPC" means in this context. If you can just share a mapping, yes it's going to be quite fast. If you need to wait for approval to come back, it's going to take more time. If you can't share a memory segment, even more time.
No idea what this vibe code is doing, but two processes on the same machine can always share a mapping, though maybe your PL of choice is incapable. There aren’t many libraries that make it easy either. If it’s not two processes on the same machine I wouldn’t really call it IPC.
Of course a round trip will take more time, but it’s not meaningfully different from two one-way transfers. You can just multiply the numbers I said by two. Generally it’s better to organize a system as a pipeline if you can though, rather than ping ponging cache lines back and forth doing a bunch of RPC.
Re: Java FFM zero-copy transport using io_uring
#46Re: Java FFM zero-copy transport using io_uring
#47Earlier quoted context omitted.
For your pet project? No. For something you're building for others to use? Almost certainly yes.
You do realize that it's possible to ask AI to write code and then read the code yourself to ensure it's valid, right? I usually try to strip the pointless comments, but it's not the end of the world if people leave them in.
IMO reading code is usually harder than writing code.
Re: Java FFM zero-copy transport using io_uring
#48This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
Apologies! It's a long read and was the only time I did not want to use AI to summarize for a purpose :) ---- So Yes, a lot of the code has been written using AI. I have also been transparent about it on https://www.mvp.express/philosophy/ in the section "AI-Assisted Development". However, that does not mean that I as the author do not understand the code/concepts :) I also don't deny the fact that I might not have g…
[deleted]
Re: Java FFM zero-copy transport using io_uring
#49This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
Okay, but is that a bad thing?
Is it bad if the world runs on a quadrillion lines of AI-generated code that no one really understands?
Re: Java FFM zero-copy transport using io_uring
#50Earlier quoted context omitted.
Vibe coding doesnt mean the author doesnt understand their code. Its likely that they don't want carpal tunnel from typing out trivial code and hence offload that labor to a machine.
"Vibe-coding" means the author deliberately does not understand their code. "AI-assisted engineering" is what you are thinking of.
Well, it is the original poster that used vibe-coding as "AI-assisted engineering".