node/metabase: Interrupt search by primary filter faster

Primary filters are applied to sorted meta bucket's elements. This
allows us to speed up execution when we reached mismatch at some point:
 - for EQ/PREFIX/LT/LE/GE matchers, any next item will definitely fail;
 - for GT matcher, any next item will definitely fail if some previous
 element matched.

Now the meta bucket iterator breaks when the mentioned conditions are
reached. This speeds up the processing of most search queries,
especially as the number of objects increases.

Refs #3058.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>

pkg/local_object_storage/metabase/metadata.go

@@ -433,6 +433,7 @@ func (db *DB) searchTx(tx *bbolt.Tx, cnr cid.ID, fs object.SearchFilters, fInt m
 	var more bool
 	var id, dbVal, primDBVal []byte
 	var keyBuf keyBuffer
+	var wasPrimMatch bool
 	attrSkr := &metaAttributeSeeker{keyBuf: &keyBuf, bkt: metaBkt}
 	curEpoch := db.epochState.CurrentEpoch()
 	dbValInt := new(big.Int)
@@ -475,8 +476,12 @@ nextPrimKey:
 					matches = matchValues(checkedDBVal, mch, fltVal)
 				}
 				if !matches {
+					if mch != object.MatchStringNotEqual && (wasPrimMatch || mch != object.MatchNumGT) {
+						break nextPrimKey
+					}
 					continue nextPrimKey
 				}
+				wasPrimMatch = true
 				// TODO: attribute value can be requested, it can be collected here, or we can
 				//  detect earlier when an object goes beyond the already collected result. The
 				//  code can become even more complex. Same below