http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Configurator, In constantly changing requirement, you are likely to _need_ those fields later on, no? And even so, you aren't likely to get that in actual production system.http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment10http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment10Sat, 16 Mar 2013 05:16:20 GMTSure, but with constantly changing requirements you could end up with dozens of fields being indexed.http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment9http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment9Fri, 15 Mar 2013 10:47:57 GMTConfigurator, Not really, no. The cost of indexing another field vs. the cost of maintaining another index is several orders of magnitudes. http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment8http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment8Fri, 15 Mar 2013 04:12:25 GMTSuppose I have query that uses values A and B; it will create an auto index on A and B. I then change my query to use values B and C instead - the index will be expanded to index all of A, B and C. But if I never query by A again, isn't this a bit of a waste?http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment7http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment7Thu, 14 Mar 2013 21:14:35 GMTMatt, We are using build 1.0.960. http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment6http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment6Thu, 07 Mar 2013 23:34:03 GMTChad, The 2.5 experimental builds.http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment5http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment5Thu, 07 Mar 2013 14:46:26 GMTAfif, We improved on the "new index" story as well. But now that the QO takes this into account, if there is an existing index that can serve ,it will use that.http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment4http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment4Thu, 07 Mar 2013 14:17:57 GMT@Afif The index definately should return results whilst it is stale. It will however not return results for the most recently inserted docs as it indexes in insert order. What build are you using? You might want to post an issue on the mailing list, https://groups.google.com/forum/#!forum/ravendb Also with the latest builds the indexing times have fallen, see http://ayende.com/blog/160033/what-is-up-with-ravendb-2-0-performance for instancehttp://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment3http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment3Thu, 07 Mar 2013 12:23:10 GMTWhich build will these new index related features be in? http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment2http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment2Thu, 07 Mar 2013 01:05:06 GMTfrom our experience of ravendb in production when you have a few million records, a new index is stale for hours. worse still many times when the index goes stale, it returns no results, as opposed to always returning what is already indexed. http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment1http://ayende.com/161283/rob-s-sprint-query-optimizer-jumped-a-grade#comment1Wed, 06 Mar 2013 12:41:32 GMT