928 karma · joined September 3, 2015
On my ryzen 9 it needs around 8 cores to do the same work in a threaded io loop than you can do single threaded. And the mechanism doesnt matter, you could share an fd, use SO_REUSEPORT or just share memory between threads.
Just doing the sharing makes everything extremely slow. One context switch becomes more expensive than just doing it single threaded.
But that’s what i wanted, I was looking for a native device to test my apps and libs on to see how they perform on a constrained device.
I got a Ryzen 9 in a desktop when I need speed.
I’ve bought my last MacBook Pro in 2015 and replaced it with a framework 12 this year.
Hopefully this will get us recycling friendly plastics for foods in the long run since those just get burned nowadays cause you can’t recycle those we have today for that job.
And there is a saying where I grew up: you need a village to raise a kid, I feel like we lost track of that and feel the issues of that now.
Btw, von der leyen is trying to get stuff like this written down as laws since 2009, it got her the nickname Zensursula.
There are very few laws which can say what you are allowed to do with your owned house. One of them is when it is of historical value. Then you aren’t allowed to change pretty much anything.
The rest are just landlords who want to fuck you over.
Will be fun when those see a whole new http verb, I bet that leads to at least DoS by the track record of that company.
Gotta read the usual sources to find out what you gotta disable on your machines, like you have to for every single syscall since forever.
The two things that make io_uring fast are chaining of operations and zero syscall mode, the former would require that all async io frameworks/libs would need to be rewritten to make use of that and then all user facing apps would also need to be rewritten since all you’d get now are completions to operations instead of waiting if you can run a operation.
Do you drive to Norway for your beach holiday?