vinyl: fix latency accounting for point lookups
We don't account latency of point lookups, neither we emit a warning if a point lookup took > too_long_threshold. To fix this, let's move the too_long_threshold configuration parameter from vy_env to vy_index_env and check it in both vy_read_iterator_next() and vy_point_lookup(). This will also allow us not to pass too_long_threshold (or vy_env for that matter) all the way down to read iterator initialization.
Showing
- src/box/vinyl.c 4 additions, 13 deletionssrc/box/vinyl.c
- src/box/vy_index.c 1 addition, 0 deletionssrc/box/vy_index.c
- src/box/vy_index.h 5 additions, 0 deletionssrc/box/vy_index.h
- src/box/vy_point_lookup.c 14 additions, 1 deletionsrc/box/vy_point_lookup.c
- src/box/vy_read_iterator.c 2 additions, 4 deletionssrc/box/vy_read_iterator.c
- src/box/vy_read_iterator.h 1 addition, 7 deletionssrc/box/vy_read_iterator.h
- test/vinyl/errinj.result 25 additions, 1 deletiontest/vinyl/errinj.result
- test/vinyl/errinj.test.lua 8 additions, 0 deletionstest/vinyl/errinj.test.lua
Loading
Please register or sign in to comment