On Fri, Jun 20, 2014 at 8:00 PM, Cindy Hsin <[email protected]> wrote:
> Hi, Mike: > > Since both ES and Solr uses Lucene, do you know why we only see big ingest > performance degradation with ES but not Solr? > I'm not sure why: clearly something is slow with ES as you add more and more fields. I think it has to do with how it manages its mappings. > Are you suggesting that if our customer require large amount of Metadata > field, even Solr won't be able to provide decent performance when ingest > and search are happening concurrently? > Exactly. Even if you/we fixed ES's slowness as you add tons of fields, or if you went with Solr, you're still going to see poor indexing/merging/searching performance because Lucene itself doesn't scale very well to so many fields: this use case (tons of fields) has never been a priority for Lucene developers because it's typically easy for the application to change its approach to not use so many fields. Mike McCandless http://blog.mikemccandless.com -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAD7smRce61ZAPYv2zdFfFqjQ_onvCWN3K6Qopu6-iG1aa9MHNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
