That works fine as long as nobody actually uses the unhappy path. If major libraries and frameworks do it all the time, you lose. So there is a certain aspect of culture outside what the language itself is capable of…
There are certainly hardware implementations of FFTs, in high-speed communications systems and the likes. So it's not just theoretical :-)
You still need at least one IPv4 address somewhere if you want to send ICMP back, yes. (Typically a loopback, i.e., something not connected to a specific interface. Routers use loopback interfaces for rather different…
More like, the point is to facilitate turning off IPv4. It's much nicer to manage a single-stacked backbone, but you still need IPv4 out in the edges somehow (for many cases, anyway). I guess this is another way to do…
I wish I knew about this algorithm when I worked in databases; it would be well-suited for window functions (even over floats for most users). Now I think I've seen it described two or three different places :-)
A friend and I bought RAM for our aging servers at eBay in 2024. That was 512GB (16x32GB -- we split it equally) of DDR4 ECC 2133MHz, registered. For… $536.86 plus shipping. Somehow it feels like we got a pretty good…
Alexa was the 39th most popular baby girl name in the US in 2006. It is… not as popular for baby girls now.
> but the point of CVEs is to let you make judgement calls Realistically, most admins cannot make judgment calls about 1000+ CVEs for a kernel release.
I've used LZO as a spam classifier on chat. Spam tends to be very content-less and repetitive...
Match-finding does not need to be quadratic. However, truly optimal gzip block splitting is very slow, indeed.
You're probably thinking of https://github.com/simonlindholm/decomp-permuter, which is used across many more decomp projects (and can do a lot more than swap lines). It's a huge help, but it's by no means enough for all…
> It’s AOT dynamic recompilation and the original IP isn’t distributed. The Git repository contains tens of thousands of lines of assembler code that seem to come from the original.
They are designed by different teams and have different ways of doing math. You could just as easily say “why are the efficiency cores wasting an extra cycle for each multiplication doing fixups of an uncommon case”.…
I think calling GEQO generative is a bit of a stretch; it's just a different way of searching through the same space with the same cost model. More or less devolving to “let's take a bunch of randomized join orders and…
GEQO is not to get a better plan than the traditional optimizer, it is to be able to get a plan at all when the query is large. And it's widely known for creating poor plans.
There are papers and Postgres projects that attempt this kind of learning-based optimization, with some success. None are in widespread use. (One part, but certainly not the entirety, of the problem is that it's not…
This immediately halves your throughput.
The immediate problem: How do you know which one is better without running them?
“Phoronix, but high quality” would also be great. People kept asking if they could pay for AnandTech, and they said “we'll think about it” for years until they shut down instead because it was financially unsustainable.
Still, we're talking orders of magnitude here. I've fed Shazam with a stream of the cheapest lapel microphone you could get, mounted behind a rack filled with twelve very noisy servers, in a hall filled with 5000 people…
For me, mostly a lot of false negatives. I have a Pixel 8, and I have no problems using the microphone normally, but somehow, Merlin requires the bird to be within a couple of meters of me and sing for quite a while…
For any complex system, there's never one single trick or design choice that makes it fast. It's always a large amount of engineering (or exaggerations, of course).
Yes. Especially when there are common libraries and you can reuse their names, structures or even entire decompiled routines. There's a fair amount of folklore going around, but less direct sharing than would be ideal.
> Historically there was a notion of "clean room" reimplementation These projects start off with the original assembly code and use it actively throughout all stages. This is about as far away from clean room as you get.
> I think he's saying that building a browser is not a transferrable skill, like making a generic web page is. Employers don't like specialists. I recently switched roles, and among the seven places I interviewed, none…
That works fine as long as nobody actually uses the unhappy path. If major libraries and frameworks do it all the time, you lose. So there is a certain aspect of culture outside what the language itself is capable of…
There are certainly hardware implementations of FFTs, in high-speed communications systems and the likes. So it's not just theoretical :-)
You still need at least one IPv4 address somewhere if you want to send ICMP back, yes. (Typically a loopback, i.e., something not connected to a specific interface. Routers use loopback interfaces for rather different…
More like, the point is to facilitate turning off IPv4. It's much nicer to manage a single-stacked backbone, but you still need IPv4 out in the edges somehow (for many cases, anyway). I guess this is another way to do…
I wish I knew about this algorithm when I worked in databases; it would be well-suited for window functions (even over floats for most users). Now I think I've seen it described two or three different places :-)
A friend and I bought RAM for our aging servers at eBay in 2024. That was 512GB (16x32GB -- we split it equally) of DDR4 ECC 2133MHz, registered. For… $536.86 plus shipping. Somehow it feels like we got a pretty good…
Alexa was the 39th most popular baby girl name in the US in 2006. It is… not as popular for baby girls now.
> but the point of CVEs is to let you make judgement calls Realistically, most admins cannot make judgment calls about 1000+ CVEs for a kernel release.
I've used LZO as a spam classifier on chat. Spam tends to be very content-less and repetitive...
Match-finding does not need to be quadratic. However, truly optimal gzip block splitting is very slow, indeed.
You're probably thinking of https://github.com/simonlindholm/decomp-permuter, which is used across many more decomp projects (and can do a lot more than swap lines). It's a huge help, but it's by no means enough for all…
> It’s AOT dynamic recompilation and the original IP isn’t distributed. The Git repository contains tens of thousands of lines of assembler code that seem to come from the original.
They are designed by different teams and have different ways of doing math. You could just as easily say “why are the efficiency cores wasting an extra cycle for each multiplication doing fixups of an uncommon case”.…
I think calling GEQO generative is a bit of a stretch; it's just a different way of searching through the same space with the same cost model. More or less devolving to “let's take a bunch of randomized join orders and…
GEQO is not to get a better plan than the traditional optimizer, it is to be able to get a plan at all when the query is large. And it's widely known for creating poor plans.
There are papers and Postgres projects that attempt this kind of learning-based optimization, with some success. None are in widespread use. (One part, but certainly not the entirety, of the problem is that it's not…
This immediately halves your throughput.
The immediate problem: How do you know which one is better without running them?
“Phoronix, but high quality” would also be great. People kept asking if they could pay for AnandTech, and they said “we'll think about it” for years until they shut down instead because it was financially unsustainable.
Still, we're talking orders of magnitude here. I've fed Shazam with a stream of the cheapest lapel microphone you could get, mounted behind a rack filled with twelve very noisy servers, in a hall filled with 5000 people…
For me, mostly a lot of false negatives. I have a Pixel 8, and I have no problems using the microphone normally, but somehow, Merlin requires the bird to be within a couple of meters of me and sing for quite a while…
For any complex system, there's never one single trick or design choice that makes it fast. It's always a large amount of engineering (or exaggerations, of course).
Yes. Especially when there are common libraries and you can reuse their names, structures or even entire decompiled routines. There's a fair amount of folklore going around, but less direct sharing than would be ideal.
> Historically there was a notion of "clean room" reimplementation These projects start off with the original assembly code and use it actively throughout all stages. This is about as far away from clean room as you get.
> I think he's saying that building a browser is not a transferrable skill, like making a generic web page is. Employers don't like specialists. I recently switched roles, and among the seven places I interviewed, none…