|
|
|
|
|
by marcuslager
3264 days ago
|
|
I'm glad I posted here because one point is maybe finally clear to me about speed. It's not a good word for performance. It's the wrong word to use. The great folks at Elasticsearch would _love_ for Lucene to be more performant. It would make life so much easier for them. The Lucene team spend a good buck on their nightly performance tests. It's astonishing how well-tested Lucene is. I wonder why I'm faster at writing and reading. Maybe it's because I have been benchmarking against an older version (4.8). But still. I wonder if my tests are all wrong or if I just got lucky in my design. ResinDB has flaws. It puts massive pressure on GC at writing time, if your batches are huge. I'm working hard at optimizing that achilees heel away. Before I have completely done so, writing speed is achieved through lots of memory allocations. It's surprisingly easy though to move away from using GC as a service. But performance is not a feature anymore? Edit:typos and tried to clarify things |
|