-
Notifications
You must be signed in to change notification settings - Fork 872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
poor performance for order clause #5680
Comments
can you post the explain of this query?
|
here is the explain:
|
any idea to improve performance for order by alias property like following query? SELECT in AS rid , in.ctime as ctime FROM list WHERE out = #16:5 ORDER BY (ctime DESC) LIMIT 13 |
no update? |
how much is the execution time? |
more than 20 seconds for 30k records. feel very upset about this database already as we don't think it is capable for production. |
can you post the explain of this
and the result of this?
Thanks |
can you try it at your side with database has 30k records. I'm sure you will have really suck performance for order by alias property. |
hi @martingg88 we could speed up things if you can send me a test db where i can try your queries and help you optimize it. My email is e.risa@orientdb.com |
guys the issue is your side didn't optimize performance for query that have order clause with alias property. Please check with you team. I'm sorry that i can't send you the db as it is confidential data for my client. |
The following query take about 2 to 3 seconds from 80k records even though i already index out property. any idea?
SELECT in AS rid FROM list WHERE out = #16:5 ORDER BY (@Rid DESC) LIMIT 13
The text was updated successfully, but these errors were encountered: