![]() With this change, there are no more memory allocations in the calls to PostingsIterator.Next() in the micro benchmarks of bleve-query. On a dev macbook, on an index of 50K wikipedia docs, using high frequency search of "text:date"... 400 qps - upsidedown/moss 565 qps - scorch before 680 qps - scorch after |
||
---|---|---|
.. | ||
scorch | ||
store | ||
upsidedown | ||
analysis.go | ||
field_cache.go | ||
index.go |