Hi all, I'm having severe problems with OrientDB 2.1.16 at the moment. The performance of my website, a social network, has become extremely slow in the past weeks. I've enabled performance checkpoints in my code and it seems even simple unique key lookups are costing a lot of time.
Basically, all my entities have an 'ID' field of type STRING which are each indexed by a UNIQUE_HASH_INDEX. Vertex and edge lookups should be extremely fast! But my logs indicate delays of 10ms to 20ms per single entity. I'm loading a lot of relationships and in the end, my main page takes about 15 seconds to load, which is WAY to long for any webpage. I've tried rebuilding all my indexes, but no change. I also tried rebooting the server. The database is hosted on a single node on an AWS server (t2.medium instance). I don't know if this is relevant, but I also seemed to be receiving more ConcurrentModificationExceptions (which I handle by retrying the transaction) than usual. In fact, I've received quite a few while I was the only user on the entire website, which was strange. I'm also running a demo version of my website, with a lot less data, and it's not as slow. So it seems to get exponentially slower the more data I have, although I really don't have that much data to begin with (about 5,000 vertices and 10,000 edges). Can you guys please give me some pointers on how I can further debug this? The future of my website depends on it -- I can't go on with this kind of performance, and I barely have any users online to begin with. Best regards, Jean -- --- 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.
