Hi! Some time ago Luka asked, how people use Orient DB. Ok, I just finished testing it as a possible platform for migration from Alfresco ECM repository (yes, Alfresco is much more than just a repo, but anyway) for a big enterprise web app
First of all - v2.2 is much better than 2.0 in both stability and performance, good job done Storage looks robust, there were couple of issues (#6542 and #6578) IMHO main bottleneck now is query planning, optimisation and automatic usage of indexes. Yes, I know how much IBM, Oracle and MS spent on that, but still - we are not talking about statistical optimisation etc. Queries like select from person where name like 'joh%' should use indexes, you couldnt outperform relation db without that It is hard to select right index type, IMHO there should be more universal type - Any type doesnt handle LIKE - SBTree and Hash doesnt handle CONTAINSTEXT - Fulltext and Lucene doesnt handle = (simple equal) In the case of web app with embedded OrientDB, there is strange situation with caching. Well, we have a lot of caches - L1 cache in transaction (yes, it is enterprise, transactions is a must have, thats why Orient...) - Our app relies on REPEATABLE READ, so another cache for all records read (it intersects with L1, isnt it?) - Local cache in database instance. Problem is that it is cleaned on close (when returned to the pool), for embedded mode in web app it means on every client request, so really that cache works nearly as L1 (one request ~ one transaction) - It seems that the only cache that survives between requests is a storage cache. But it caches pages, a little bit too low-level As a result, I have big performance gain using small app-level cache (L1+L2), which caches mainly master data (it is nearly-constant info). IMHO too many caches onboard :) Again - if you need transactional nosql db, Orient looks promising -- --- 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.
