Hi Shrikant, There are at least two factors that can impact performance here:
- OrientDB does some caching of SQL statements, so the first time you execute a query it has to be parsed from scratch, while the second time you will have the AST in cache - there is a layer, called diskCache, that keeps recently used data in memory, so that you don't have to access disk to query it, probably this is the part that impacts your case the most Thanks Luigi 2017-11-03 9:00 GMT+01:00 shrikant pachauri <sk.pach.1...@gmail.com>: > > Greeting > > I am trying to insert say 10k vertices in graph DB. I am using a script > file in javascript where I am using Orient DBs native query language. Now > after creating a class from the vertices when i ran the query for the first > time it takes me about 2.51s. Now if I ran the same query again it takes me > about 0.92s to insert the 10k records. > > Now my question is this is there any sort of caching or some other > mechanism which makes my execution of the second query faster than before. > I have a perspective that May be it stored the compiled query of the first > time and it does not need to compile the query next time in case it > encounter the same query. > > Any help would be appreciated > > -- > > --- > 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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
