On Sep 22, 2010, at 11:04 AM, Smiley, David W. wrote: > Speaking of performance, on a large scale search project where we're using > Solr in place of a MarkLogic prototype (because ML is so friggin expensive, > for one reason), the search results were so fast (~150ms) vs. the ML's > results of 2-3 seconds, that the UI engineers building the interface on top > of the XML output thought Solr was broken because it was so fast. The quote > was "It's so fast, it's broken". In other words, they were used to 2-3 > second response times and so if the results came back as fast as what Solr > has been doing, then surely there's a bug. There's no bug. :) Admittedly, I > think it was a bit of an apples and oranges comparison but I love that quote > nonetheless.
I implemented Solr at Netflix and now I work at MarkLogic, and I strongly agree that the comparison is apples and oranges. MarkLogic does run very fast on very large datasets, so maybe that prototype was built to show functionality instead of speed. Also, MarkLogic already has a lot of stuff that is still in the future for Solr, like true real-time search, updating fields, and geospatial search. Next time, invite the MarkLogic people, too. :-) wunder -- Walter Underwood Lead Engineer MarkLogic
