Hi Simon, To avoid the cost of re-opening the database you should be sticky to the same server (until it become unreachable).
Please consider also to execute multiple operation in one call by using the SQL Batch: https://github.com/orientechnologies/orientdb/wiki/SQL-batch Lvc@ On 22 July 2014 23:50, Simon L <[email protected]> wrote: > Hi there, > > We have a very large site with tons of users making numerous queries. > We're using Node.JS with Backbone, and OrientDB as the backend DB. > There will be multiple webservers and multiple OrientDB servers. > > What are the recommendations for lowering the overheads of constantly > reconnecting to OrientDB? > > I was thinking of connecting with the REST API with OSESSIONID. Maybe > there's a better way? > We aren't sure about using sticky or non-sticky sessions just yet. We're > open to both options. > > -- > > --- > 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
