Mihai Bucica
2018-09-30 22:36:12 UTC
Hello,
The query execution time in OrientDB Studio(or console.sh w/remote mode)
seems to be computed locally in browser and will roughly be 'server
execution time for query' + 'network latency' (RTT)
Many times when working from my personal laptop against cloud hosted
OrientDB instance means having network latency for hundreds
milliseconds....and for a long time I thought OrientDB is really slow.
So when trying to optimize queries running them from the same machine
where OrientDB server runs makes a big difference.
Wouldn't be more easy for the server to send in query response something
like 'server execution time for query' ?
Thanks,
Mihai
The query execution time in OrientDB Studio(or console.sh w/remote mode)
seems to be computed locally in browser and will roughly be 'server
execution time for query' + 'network latency' (RTT)
Many times when working from my personal laptop against cloud hosted
OrientDB instance means having network latency for hundreds
milliseconds....and for a long time I thought OrientDB is really slow.
So when trying to optimize queries running them from the same machine
where OrientDB server runs makes a big difference.
Wouldn't be more easy for the server to send in query response something
like 'server execution time for query' ?
Thanks,
Mihai
--
---
You received this message because you are subscribed to the Google Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
---
You received this message because you are subscribed to the Google Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.