Skip to content

Commit 6b461bd

Browse files
authored
fix example with new names
1 parent 16001a3 commit 6b461bd

File tree

1 file changed

+24
-24
lines changed

1 file changed

+24
-24
lines changed

content/commands/ft.profile.md

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ Iterator types include:
133133

134134
**Notes on `Number of reading operations` and `Estimated number of matches`**
135135

136-
`Number of reading operations` is the number of times an iterator was interacted with. A very high value in comparison to others is a possible warning flag. `NUMERIC` and `Child iterator` types are broken into ranges, and `Number of reading operations` will vary depending on the range. For `UNION`, the sum of the counters in child iterators should be equal or greater than the child iterator's counters.
136+
`Number of reading operations` is the number of times an iterator was interacted with. A very high value in comparison to others is a possible warning flag. `NUMERIC` and `Child iterator` types are broken into ranges, and `Number of reading operations` will vary depending on the range. For `UNION`, the sum of the reading operations in child iterators should be equal or greater than the child iterator's reading operations.
137137

138138
`Estimated number of matches` is the size of the document set. `Number of reading operations` should always be equal or less than `Estimated number of matches`.
139139

@@ -243,7 +243,7 @@ Here's an example of running the `FT.PROFILE` command for a compound query.
243243
2) INTERSECT
244244
3) Time
245245
4) "0"
246-
5) Counter
246+
5) Number of reading operations
247247
6) (integer) 6
248248
7) Child iterators
249249
8) 1) Type
@@ -252,7 +252,7 @@ Here's an example of running the `FT.PROFILE` command for a compound query.
252252
4) UNION
253253
5) Time
254254
6) "0"
255-
7) Counter
255+
7) Number of reading operations
256256
8) (integer) 6
257257
9) Child iterators
258258
10) 1) Type
@@ -261,7 +261,7 @@ Here's an example of running the `FT.PROFILE` command for a compound query.
261261
4) UNION
262262
5) Time
263263
6) "0"
264-
7) Counter
264+
7) Number of reading operations
265265
8) (integer) 4
266266
9) Child iterators
267267
10) 1) Type
@@ -270,37 +270,37 @@ Here's an example of running the `FT.PROFILE` command for a compound query.
270270
4) kids
271271
5) Time
272272
6) "0"
273-
7) Counter
273+
7) Number of reading operations
274274
8) (integer) 4
275-
9) Size
275+
9) Estimated number of matches
276276
10) (integer) 4
277277
11) 1) Type
278278
2) TEXT
279279
3) Term
280280
4) +kid
281281
5) Time
282282
6) "0"
283-
7) Counter
283+
7) Number of reading operations
284284
8) (integer) 4
285-
9) Size
285+
9) Estimated number of matches
286286
10) (integer) 4
287287
11) 1) Type
288288
2) TEXT
289289
3) Term
290290
4) small
291291
5) Time
292292
6) "0"
293-
7) Counter
293+
7) Number of reading operations
294294
8) (integer) 2
295-
9) Size
295+
9) Estimated number of matches
296296
10) (integer) 2
297297
9) 1) Type
298298
2) UNION
299299
3) Query type
300300
4) TAG
301301
5) Time
302302
6) "0"
303-
7) Counter
303+
7) Number of reading operations
304304
8) (integer) 6
305305
9) Child iterators
306306
10) 1) Type
@@ -309,44 +309,44 @@ Here's an example of running the `FT.PROFILE` command for a compound query.
309309
4) new
310310
5) Time
311311
6) "0"
312-
7) Counter
312+
7) Number of reading operations
313313
8) (integer) 4
314-
9) Size
314+
9) Estimated number of matches
315315
10) (integer) 10
316316
11) 1) Type
317317
2) TAG
318318
3) Term
319319
4) used
320320
5) Time
321321
6) "0"
322-
7) Counter
322+
7) Number of reading operations
323323
8) (integer) 4
324-
9) Size
324+
9) Estimated number of matches
325325
10) (integer) 8
326326
6) 1) Result processors profile
327327
2) 1) Type
328328
2) Index
329329
3) Time
330330
4) "0"
331-
5) Counter
331+
5) Results processed
332332
6) (integer) 3
333333
3) 1) Type
334334
2) Scorer
335335
3) Time
336336
4) "0"
337-
5) Counter
337+
5) Results processed
338338
6) (integer) 3
339339
4) 1) Type
340340
2) Sorter
341341
3) Time
342342
4) "0"
343-
5) Counter
343+
5) Results processed
344344
6) (integer) 3
345345
5) 1) Type
346346
2) Loader
347347
3) Time
348348
4) "0"
349-
5) Counter
349+
5) Results processed
350350
6) (integer) 3
351351
{{< / highlight >}}
352352
</details>
@@ -403,32 +403,32 @@ Here's an example of running the `FT.PROFILE` command for a vector query.
403403
2) VECTOR
404404
3) Time
405405
4) "0"
406-
5) Counter
406+
5) Number of reading operations
407407
6) (integer) 3
408408
6) 1) Result processors profile
409409
2) 1) Type
410410
2) Index
411411
3) Time
412412
4) "0"
413-
5) Counter
413+
5) Results processed
414414
6) (integer) 3
415415
3) 1) Type
416416
2) Metrics Applier
417417
3) Time
418418
4) "0"
419-
5) Counter
419+
5) Results processed
420420
6) (integer) 3
421421
4) 1) Type
422422
2) Sorter
423423
3) Time
424424
4) "0"
425-
5) Counter
425+
5) Results processed
426426
6) (integer) 3
427427
5) 1) Type
428428
2) Loader
429429
3) Time
430430
4) "0"
431-
5) Counter
431+
5) Results processed
432432
6) (integer) 3
433433
{{< /highlight >}}
434434
</details>

0 commit comments

Comments
 (0)