From: Serge Petrenko <sergepetrenko@tarantool.org> To: korablev@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH v3 2/2] box: refactor tuple_field_raw to omit path checks Date: Fri, 4 Dec 2020 12:52:55 +0300 [thread overview] Message-ID: <2cf30fdbec386295dd853a8e94ade5582ddae8b6.1607075291.git.sergepetrenko@tarantool.org> (raw) In-Reply-To: <cover.1607075291.git.sergepetrenko@tarantool.org> tuple_field_raw is an alias to tuple_field_raw_by_path with zero path. This involves multiple path != NULL checks which aren't needed for tuple field access by field number. The checks make this function rather slow compared to its 1.10 counterpart (see results below). In order to fix perf problems when JSON path indices aren't involved, factor out the part of tuple_field_raw_by_path which is responsible for direct field access by number and place it in tuple_field_raw. This patch was tested by snapshot recovery part involving secondary index building for a 1.5G snapshot with one space and one secondary index over 4 integer and one string field. Comparison table is below: Version | time(seconds) | Change relative to 1.10 ---------------|----------------|------------------------ 1.10 | 2:24 | -/- 2.x(unpatched) | 3:03 | + 27% 2.x (patched) | 2:10 | - 10% Numbers below show cumulative time spent in tuple_compare_slowpath, for 1.10 / 2.x(unpatched) / 2.x(patched) for 15, 19 and 14 second profiles respectively: 13.9 / 17.8 / 12.5. tuple_field_raw() isn't measured directly, since it's inlined, but all its uses come from tuple_compare_slowpath. As the results show, we manage to be even faster, than 1.10 used to be in this test. This must be due to tuple comparison hints, which are present only in 2.x. Closes #4774 --- src/box/tuple.h | 29 +++++++++++++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/src/box/tuple.h b/src/box/tuple.h index 755aee506..fd373fdbf 100644 --- a/src/box/tuple.h +++ b/src/box/tuple.h @@ -697,8 +697,33 @@ static inline const char * tuple_field_raw(struct tuple_format *format, const char *tuple, const uint32_t *field_map, uint32_t field_no) { - return tuple_field_raw_by_path(format, tuple, field_map, field_no, - NULL, 0, NULL, MULTIKEY_NONE); + if (likely(field_no < format->index_field_count)) { + int32_t offset_slot; + uint32_t offset = 0; + struct tuple_field *field; + if (field_no == 0) { + mp_decode_array(&tuple); + return tuple; + } + struct json_token *token = format->fields.root.children[field_no]; + field = json_tree_entry(token, struct tuple_field, token); + offset_slot = field->offset_slot; + if (offset_slot == TUPLE_OFFSET_SLOT_NIL) + goto parse; + offset = field_map_get_offset(field_map, offset_slot, MULTIKEY_NONE); + if (offset == 0) + return NULL; + tuple += offset; + } else { +parse: + ERROR_INJECT(ERRINJ_TUPLE_FIELD, return NULL); + uint32_t field_count = mp_decode_array(&tuple); + if (unlikely(field_no >= field_count)) + return NULL; + for ( ; field_no > 0; field_no--) + mp_next(&tuple); + } + return tuple; } /** -- 2.24.3 (Apple Git-128)
next prev parent reply other threads:[~2020-12-04 9:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-04 9:52 [Tarantool-patches] [PATCH v3 0/2] reduce performance degradation introduced by JSON path indices Serge Petrenko 2020-12-04 9:52 ` [Tarantool-patches] [PATCH v3 1/2] box: speed up tuple_field_map_create Serge Petrenko 2020-12-10 17:17 ` Nikita Pettik 2020-12-11 6:34 ` Serge Petrenko 2020-12-11 14:32 ` Nikita Pettik 2020-12-04 9:52 ` Serge Petrenko [this message] 2020-12-10 17:25 ` [Tarantool-patches] [PATCH v3 2/2] box: refactor tuple_field_raw to omit path checks Nikita Pettik 2020-12-11 6:36 ` Serge Petrenko 2020-12-10 17:35 ` [Tarantool-patches] [PATCH v3 0/2] reduce performance degradation introduced by JSON path indices Nikita Pettik 2020-12-11 6:47 ` Serge Petrenko 2020-12-11 13:39 ` Alexander V. Tikhonov 2020-12-11 14:51 ` Nikita Pettik
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=2cf30fdbec386295dd853a8e94ade5582ddae8b6.1607075291.git.sergepetrenko@tarantool.org \ --to=sergepetrenko@tarantool.org \ --cc=korablev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 2/2] box: refactor tuple_field_raw to omit path checks' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox