search

edualc / lqo_ml_perspective

This repository includes the code base used in the paper "Is Your Learned Query Optimizer Behaving As You Expect? A Machine Learning Perspective", accepted at VLDB2024, the 50th International Conference on Very Large Databases.
7 stars 3 forks source link

NEO is extremlly slow #1

Open NLGithubWP opened 3 days ago

NLGithubWP commented 3 days ago

I have set up the code based on the readme and tried to run the NEO on the JOB datasets again.

However, I found the NEO is extremely slow, with some queries even consuming 39.4 minutes.

Here is the log

(ExecuteSql pid=25944) Executed Query on Postgres taking 2364003.386 (14.296 planning).

May I know what could be the reason for this?

edualc commented 3 days ago

That's generally a difficult question to answer, since your hardware, database configuration, etc. has a significant impact on your execution times.

However, in the case of Neo this is also to be expected since they do not use query timeouts in Neo (as this was one of the selling points of Balsa). That means, if Neo tries out a low quality plan it will run until completion.