Spatial in own indexes?
ZNS
I have an index that has items with lat and long-itude. I have added
spatialindex to it for searching within a radius. However it's
probably only 10% of the queries against the index that are going to
be spatial. Is it recommended to create a separate index for spatial
queries then? Will it effect performance on the other 90% of the
queries?
Matt Warren
Tobi
> The advice has always been, fewer, larger indexes have better perf that
> lots of smaller ones.
I thought it might be a good idea to test this from time to time, so I
just ran my old test program for this again:
100 Indexes with a single property each: 00:05:08
1 Index with 100 properties : 00:02:01
This is actually better than older RavenDB version, but the advice to use
few larger indexes is still valid.
Tobias
Matt Warren
Tobi
> Just out of interest, how many docs were there in Raven when you ran this?
00:05:08 vs. 00:02:01 was for 25.600 docs (each having 100 string
properties filled with guids).
> And do you know it there is more or less of a different in the timings
> when you have a larger amount of docs?
For 128.000 docs it's:
00:27:45 vs. 00:09:55
Tobias
Matt Warren
Itamar Syn-Hershko
Tobi
> Did any of those had spatial field in it?
No. Only simple string fields. Spatial fields shouldn't make much of a
difference for writes to the DB. They are just mapped as
longitude/latitude somehow in order to allow Lucene to do distance
queries, aren't they?
Tobias
