﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Janus007 commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>AG, I agree it's only 2 mill rows, Microsoft Sql will do such a search in milliseconds, no doubt about that. 

Max Mind is terrible wrong, but that is not up to discuss that :), but maybe they were talking about Excel *LOL*</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment10</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment10</guid><pubDate>Thu, 21 Jun 2012 21:22:51 GMT</pubDate></item><item><title>Ayende Rahien commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>Tobi,
I wrote a bunch of posts about materialized views a few years back, they are great, but in RDMBS they have severe limitations, and for the same reason you can't really do full denormalization during read.</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment9</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment9</guid><pubDate>Thu, 21 Jun 2012 14:42:39 GMT</pubDate></item><item><title>tobi commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>Ayende,

that might be a reason. I just know that materialized views in SQL Server are a joy to use. I write normalized, I read with full performance. Joins become no-ops at runtime. Often it is possible to save on sorting and filtering as well. Complex queries become single range scans on some index.</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment8</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment8</guid><pubDate>Thu, 21 Jun 2012 14:32:34 GMT</pubDate></item><item><title>AG commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>So equivalent sql query run on my machine (nothing special really...) and ms sql (with the database imported but no optimisation at all) takes something between 60 and 170 ms. Tried for a few IPs.
That is waaay less than several seconds, and has plenty of places it can be improved (with indexes).</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment7</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment7</guid><pubDate>Thu, 21 Jun 2012 14:17:15 GMT</pubDate></item><item><title>Ayende Rahien commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>Tobi,
Very simple reason, it is HARD to track denormalization on reads.
</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment6</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment6</guid><pubDate>Thu, 21 Jun 2012 13:57:48 GMT</pubDate></item><item><title>tobi commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>Materialized views are the genius of RavenDB.

Not sure why RavenDB tries to proliferate denormalization on the writing side. I think we should write normalized and read denormalized. That's the best of both worlds.

I think that denormalization on the writing side is generally completely misguided.</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment5</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment5</guid><pubDate>Thu, 21 Jun 2012 13:55:34 GMT</pubDate></item><item><title>Rafal commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>Index lookup in a relational database? It takes no more than few milliseconds. I don't have to do any coding to know that...
Probably MaxMind guys were talking  about database without any indexing that you get by importing the csv file in dumbest possible way. Only then it would take few seconds to do a table scan...</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment4</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment4</guid><pubDate>Thu, 21 Jun 2012 12:17:58 GMT</pubDate></item><item><title>AG commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>@Ayende of course he did, what I meant is that somebody should verify that. Perhaps he is doing something wrong there. By the size of the data, it doesn't seem to me that it should take that long.
Anyway that's a thing to try.</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment3</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment3</guid><pubDate>Thu, 21 Jun 2012 10:43:13 GMT</pubDate></item><item><title>Ayende Rahien commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>AG,
I assume that MaxMind did.</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment2</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment2</guid><pubDate>Thu, 21 Jun 2012 10:37:52 GMT</pubDate></item><item><title>AG commented on Geo Location &amp;amp; Spatial Searches with RavenDB&amp;ndash;Part IV-Searching</title><description>Has anybody tried to load it into relational database, add some indexes, and perform such query (apart from MaxMind, just to verify)?
I somehow find it hard to belive that it takes several seconds...</description><link>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment1</link><guid>http://ayende.com/156418/geo-location-spatial-searches-with-ravendb-part-iv-searching#comment1</guid><pubDate>Thu, 21 Jun 2012 10:34:00 GMT</pubDate></item></channel></rss>