Top
Best
New

Posted by polyphilz 15 hours ago

Training a 4B model to produce 81% faster query plans than Postgres(rohanbansal.com)
544 points | 115 commentspage 2
jerpint 9 hours ago|
I have a theory that soon enough every code library will ship a CLI and a very tiny finetune for that specific lib alongside it
huahaiy 11 hours ago||
81%is nothing. It is not hard to be more than 3x better than Postgres [1]. And you don’t need a model to do that, let alone a 4B model. How much additional compute is needed to just run that model?

[1] https://github.com/datalevin/datalevin/tree/master/benchmark...

rixed 5 hours ago||
It's certainly a good idea to train a neural network to find good query plans but... an LLM??
happyopossum 9 hours ago||
An 8GB dataset? That’s literally a few seconds worth of records generated in my world, and any speedup at that scale is completely meaningless.

Let’s talk when you are looking at double digit TB at a minimum.

foota 13 hours ago||
Funny enough I was thinking about something very similar to this based on the Jev model posted yesterday.
jwpapi 12 hours ago|
I’ve played with it already. I don’t think this is the use case. I think Jev’s use case is fast, cheap and somewhat easy classification. It’s not trainable in the way you would want here. Even though it’s fast it wont be faster than pgs query optimizer.

At least as I understand things.

How did you plan to use Jev for query optimization?

orliesaurus 12 hours ago||
I am still struggling to understand a use-case for Jev. Isn't what was explained in this article a classification problem? I.e. find and aggregate data?
jwpapi 2 hours ago|||
It’s classifying faster and cheaper. A lot of immediate ideas are better solved by pre-classifying + embedding, but their doom example or the wikipedia runs are one where you can’t preclassify.
odo1242 12 hours ago|||
The number of options has to be small and bounded. The query planning is more of a search/optimization problem than a classification problem since the number of options increases wildly based on query size.
ashley95 9 hours ago||
Suppose you run a platform, and you run a couple thousand different queries of different types throughout the day. It would make sense to have an auto-optimizer that would read long queries, ponder over them with an LLM, come up with some good plans, and store them as hints. This seems like quite a good idea? Is there a product for this?
maxrumpf 13 hours ago||
such a (visually) beautiful blogpost.
darepublic 10 hours ago||
Mentioned elsewhere but classic ml seems the right tool for this problem
anitil 10 hours ago||
> How hard can it be?

> As it turns out: enormously hard.

This exactly tracks me learning everything

evaltoken 8 hours ago|
Really creative use of distillation here.
More comments...