867110e03b
improvements uncovered some issues with how k/v data was copied or not. to address this, kv abstraction layer now lets impl specify if the bytes returned are safe to use after a reader (or writer since writers are also readers) are closed See index/store/KVReader - BytesSafeAfterClose() bool false is the safe value if you're not sure it will cause index impls to copy the data Some kv impls already have created a copy a the C-api barrier in which case they can safely return true. Overall this yields ~25% speedup for searches with leveldb. It yields ~10% speedup for boltdb. Returning stored fields is now slower with boltdb, as previously we were returning unsafe bytes. |
||
---|---|---|
.. | ||
base_test.go | ||
ordered_searchers_list.go | ||
search_boolean_test.go | ||
search_boolean.go | ||
search_conjunction_test.go | ||
search_conjunction.go | ||
search_disjunction_test.go | ||
search_disjunction.go | ||
search_fuzzy.go | ||
search_match_all_test.go | ||
search_match_all.go | ||
search_match_none_test.go | ||
search_match_none.go | ||
search_numeric_range_test.go | ||
search_numeric_range.go | ||
search_phrase_test.go | ||
search_phrase.go | ||
search_regexp_test.go | ||
search_regexp.go | ||
search_term_prefix.go | ||
search_term_test.go | ||
search_term.go |