On Wednesday, October 8, 2014 12:07:30 AM UTC-7, Jörg Prante wrote: > > With ES, you can go up to the bandwidth limit the OS allows for writing > I/O (if you disable throttling etc.) > > This means, if you write to one shard, it can be as fast as writing to > thousands of shards in parallel in summary. There is an OS limit for file > system buffers so the more shards, the more RAM is recommended. > > If OS restricts file descriptor limits and you want to write to shards, > you can estimate you need a peak of 100-200 file descriptors for active > merges etc. (this varies from version to version and from setting to > setting). ES does not impose a limit here. > > These resource demands and custom configurations are not related to the > choice SSD or HDD. > > There's no way that's true... for example, if you are on HDD, and you're index is not in memory, AND you're serving queries (which is a realistic use case) then there is NO way you can write at the full IO of the disk. It's just physically impossible.
If ES has been able to solve that problem then they could win a nobel prize :-p SSD is 2-3 orders of magnitude faster than HDD ... so yes, it is related to the choice of SSD or HDD. ... it's entirely possible I'm misinterpreting what you're saying though. -- 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/3b40a167-8f82-4f60-9833-8e3bce77370f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
