http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660The optimization is explained here: http://stackoverflow.com/questions/7640227/query-product-catalog-ravendb-store-for-spec-aggregate-over-arbitrary-collection it is minor overall.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment13http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment13Wed, 18 Apr 2012 04:55:17 GMTFelipe, No, all of those optimizations had to do with managing how we interact with Lucene, not Lucene itself.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment12http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment12Tue, 17 Apr 2012 23:56:55 GMTMicha, These posts were written two months ago, they refer to changes that went into the stable build 701. I'll discuss the exact changes in the next few posts.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment11http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment11Tue, 17 Apr 2012 23:56:07 GMTLev, We have recently significantly optimized faceted searches, so you should probably try again. What optimization did you do in the referenced code?http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment10http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment10Tue, 17 Apr 2012 23:55:05 GMT@ Lev Gorodinski Also see this thread https://groups.google.com/forum/#!msg/ravendb/GJImaCrrKkk/VVvXLXQ1RFcJ, for a discussion on other ways of improving the perf. But note that for most scenarios, the current impl is pretty quick!http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment9http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment9Tue, 17 Apr 2012 22:56:13 GMT@Lev Gorodinski Can you explain a bit more what that code sample is doing? What's the optimisation?http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment8http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment8Tue, 17 Apr 2012 22:49:30 GMTAyende, since you´re using Lucene to store Indexes, do you actually change Lucene Source Code to do improvements?http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment7http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment7Tue, 17 Apr 2012 18:09:59 GMTCall me stupid, but whatexactly is optimized now. Was the previous post written on an older version of RavenDB and this post on a current stable release after optimizations had been made? What did you change to speed up the import of the raw data for example? :) http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment6http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment6Tue, 17 Apr 2012 18:02:57 GMTAyende, are there plans to optimize faceted search in RavenDB? Or is this something that you think should be handled by a framework dedicated to search, such as Solr or ElasticSearch? I've made a simple optimization to the FacetedQueryRunner: http://pastebin.com/SRNtSaKN however I couldn't optimize much further without digging deeper into the internals.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment5http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment5Tue, 17 Apr 2012 17:57:30 GMTAyende, the indexing speed was my main concern - I was afraid that in some situations the indexing process may lag too much behind data modification and Raven would be serving strange results to users. Therefore I'm happy to see that this is not a bottleneck. A database integrated with Lucene index is a great combination and one of the biggest advantages of Ravendb imho. Updating Lucene index in realtime is tricky and difficult to do when data modifications are very frequent, so a tool that can do that automatically and almost online is very valuable.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment4http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment4Tue, 17 Apr 2012 11:50:03 GMTRafal, Those numbers are actually not that important, because we are not testing / optimizing insert performance. What we are doing is testing indexing performance, something quite different. In most systems, a RavenDB server will usually have at most one write per client request, so a few hundreds or thousands is pretty awesome in terms of the numbers of users that you can support on a single box.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment3http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment3Tue, 17 Apr 2012 10:05:37 GMTThis is afaik the first post showing some real performance numbers. And the optimized results look quite good - 1000 inserts/updates per second is fast enough for most applications. I did not yet decide to use Raven for any real application but it becomes harder to resist with every release. http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment2http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment2Tue, 17 Apr 2012 10:03:06 GMTMajor major spike for Raven. I've always loved using it but importing big data was always a hurt piece it's great to see this vast of an improvement.http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment1http://ayende.com/154913/ravendb-freedb-an-optimization-story#comment1Fri, 24 Feb 2012 14:04:26 GMT