Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

58% Positive

Analyzed from 1001 words in the discussion.

Trending Topics

#query#model#plans#plan#chess#frontier#models#training#distillation#wouldn

Discussion (23 Comments)Read Original on HackerNews

devsda•about 1 hour ago
> Frontier intelligence is extremely powerful; the distillation I did off Astra trajectories is proof enough that large models are not going anywhere

Wouldn't admitting this invite trouble due to accusations of distillation flying around between closed and open models.

pyaamb•5 minutes ago
On the flip side, its important to know just how much we would be sacrificing if big frontier gets their way in convincing the courts that distillation is a bad thing
make3•about 1 hour ago
Frontier model trainers stole almost all the data they've trained on (the whole internet, all copyrighted).

It's very hard for them to claim the moral high ground here.

It's like stealing an apple from the British Colonial Empire.

p1necone•40 minutes ago
Having the moral high ground matters less than having a big warchest of money to spend on lawyers.
kelvinjps10•35 minutes ago
Does it matter if they companies doing are not in the jurisdiction or even if they are, maybe the can't prove it?
Onavo•about 1 hour ago
I don't think anybody's denying that small models are doing distillation, the issue at hand is frontier lab vs frontier lab when it comes to big models.
foota•38 minutes ago
Funny enough I was thinking about something very similar to this based on the Jev model posted yesterday.
fsmv•about 2 hours ago
But how will you know that the query plan actually does what your query asked for?
amluto•about 2 hours ago
I would like to think that pg_hint_plan is designed in such a way that any hint it accepts must be a valid plan for the query. I’m quite confident that schemes with this property that can also express high quality plans are possible and not even excessively complicated.

This is not to say that it’s possible to genetically verify that a proposed algorithm does what you want it to — that would be undecidable or NP-hard or co-NP-hard depending on how you formulate the question.

hedgehog•about 2 hours ago
I wouldn't be very excited about adding a 4B param model to my database deployment, but using this kind of approach while testing an app to identify query plans where Postgres is leaving performance on the table seems valuable without much risk.
whazor•23 minutes ago
Given the approach from the article, you can commit the hints to git and run tests for verification. The model would be used during coding.
polyphilz•about 2 hours ago
`pg_hint_plan` has a debug log so you can verify Postgres actually used the hint or not! Used this during evaluations
timcobb•about 2 hours ago
I imagine you can perform operations on query plans to transform them and determine equivalence?
larodi•42 minutes ago
you'll have to prove equivalence through some Lean4 code perhaps? or some weird clause tree comparisons... good question indeed.
quotemstr•about 1 hour ago
Because P!=NP (very probably IMHO) there's a huge class of problem for which LLMs are useful on the expensive and heuristic-y generation side because the verification is relatively inexpensive.
KK7NIL•about 2 hours ago
"... make no mistakes" :)
Someone•about 2 hours ago
> I paid ~$800 to rent a 2x H100 SXM node from Lambda for ~95 hours, and ~$400 in OpenAI API fees to generate the Astra trajectory demonstrations.

> a tiny 4B model went from not being able to understand the harness it was wrapped in, to achieving a 1.81x geometric mean speedup and a summed latency decrease of 44.7% across a workload of join-heavy SQL queries

I can’t find it in the article (may have skimmed it too much), but I suspect they didn’t include those ~95 hours in the benchmark numbers.

I think all database vendors know their query optimizers could do much better if they could afford to spend lots of time to derive query plans.

⇒ this may be useful for some workloads, but even then, can you afford to spend hours every now and then to update your 4B model to ensure it still picks a good query plan?

dvt•about 1 hour ago
> ⇒ this may be useful for some workloads, but even then, can you afford to spend hours every now and then to update your 4B model to ensure it still picks a good query plan?

I think this would be likely comparable to a scheduled backup, so I think it would be an acceptable maintenance window. However, deterministic algorithms would likely beat re-training (or re-fine-tuning) the model. For example, one could analyze actual distributions or whatever (instead of assuming uniform), and then some plans would automatically be eliminated.

Imo a good thought experiment is to look at places that are hyper-optimized, like compilers. Would LLMs bring anything to the table (architecturally or performance-wise) to a piece of software that has been carefully crafted for decades? (Methinks no.)

btown•19 minutes ago
The Postgres query planner has had to operate, for those same decades, in a much more realtime-sensitive and restricted environment than compilers. It can only draw its conclusions from summary statistics on tables in isolation, not on their relationships with each other (and even less so when filters are involved). For many cases this is fine! For many others it isn't.
kingjimmy•about 2 hours ago
Aren't optimizations suppose to be deterministic?
cowboylowrez•about 1 hour ago
I'd like to contribute my amateur hour entry into this thread, although I did administer and develop mssql stuff for awhile.

sure optimizations based on stats, but the stats are the wildcard, in my experience query plans can change suddenly.

Queries are translated into plans according to statistics. However the transforms will be deterministic and should only change one valid plan to another. I could very easily see a neural network manipulate transforms the same way the current programming does, its just that the neural networks are by nature really nicely suitable because the "decisions" are based on training, and this training can be closed world type things like the ai assists that chess engines are now getting. Obviously ai still can't play chess but apparently its very good at ranking board positions just by developing that much statistical info because its training comes not from reading the web, but playing a gazzilian games against itself in a "closed" chess world of its own.

I'm thinking that the ai does "this legal transform of the query plan should be applied to this pattern of data (statistics, cardinality, etc)" simply because the ai encountered it in closed world training, much like the chess thing.

Just a theory tho feel free to correct!

krisoft•14 minutes ago
> Obviously ai still can't play chess

I believe you are wrong on that. Do you mean large language models can’t play chess?

tintor•about 2 hours ago
They are not. Choice among several query plans depends on various summary statistics about the data, which might not be the most recent.
cogman10•about 1 hour ago
Including the input parameters.

It's not unusual for us to end up with bad query plans because the shape of our data can vary pretty greatly. In many cases, a Foo has 1 Bar. But in some cases, a Foo has a million Bars. That can cause the query optimizer to treat lookups on the bar table as if there are few elements there (causing a scan instead of a seek).

For the general case, the optimizer gets it right. However, the fringe case is one that causes the entire system to crash. It's a bit akin to how an insertion sort can be faster than quick sort when n is small. The optimizer might make a bad assumption about the size of n which makes it pick an expensive n lookup when log(n) is available (but slower for small n).

coolThingsFirst•about 1 hour ago
why is this write-up so long?

Need 5 days just to go through it.

fennecbutt•31 minutes ago
Think of it like a paper. You wouldn't ask why a paper was so long.

Also you can now ask AI to summarise it for you and even probe with questions pertaining to your specific interests.

gonzalohm•21 minutes ago
Why wouldn't you ask that? That's exactly why papers have supplementary material
tandr•42 minutes ago
They forgot to run a (same) model to optimize article for reading speed