From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Maria Khaydich <maria.khaydich@tarantool.org>, tarantool-patches <tarantool-patches@dev.tarantool.org>, Alexander Turenko <alexander.turenko@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] box: sql prepare and execute statistics should be reflected in box.stat() Date: Thu, 13 Feb 2020 22:44:52 +0100 [thread overview] Message-ID: <d1d8fd96-340f-82b4-7d53-ebb86176928e@tarantool.org> (raw) In-Reply-To: <1581359737.397395198@f221.i.mail.ru> Hi! Thanks for the patch! On 10/02/2020 19:35, Maria Khaydich wrote: > Calling prepare and execute did not update corresponding request statistics > in the box.stat table. This happened because methods that collect stats were > never called where they should have been. > > Closes #4756 > > --- > Issue: > https://github.com/tarantool/tarantool/issues/4756 > Branch: > https://github.com/tarantool/tarantool/compare/eljashm/gh-4756-box-stat-execute-and-prepare-not-updated <https://github.com/tarantool/tarantool/issues/4756Branch:https://github.com/tarantool/tarantool/compare/eljashm/gh-4756-box-stat-execute-and-prepare-not-updated> Something is broken with the links. When I click on them, all the links are pasted into the address string of my browser concatenated. And this is what I see in the source: https://github.com/tarantool/tarantool/compare/eljashm/gh-4756-box-stat-execute-and-prepare-not-updated <https://github.com/tarantool/tarantool/issues/4756Branch:https://github.com/tarantool/tarantool/compare/eljashm/gh-4756-box-stat-execute-and-prepare-not-updated> So everything is a one huge line. This does not happen with other emails and links. See 2 comments below. > src/box/execute.c | 4 ++++ > test/box-tap/cfg.test.lua | 16 +++++++++++++--- > 2 files changed, 17 insertions(+), 3 deletions(-) > diff --git a/src/box/execute.c b/src/box/execute.c > index dc8dce81c..e775055b4 100644 > --- a/src/box/execute.c > +++ b/src/box/execute.c > @@ -732,6 +735,7 @@ sql_prepare_and_execute(const char *sql, int len, const struct sql_bind *bind, > if (sql_stmt_compile(sql, len, NULL, &stmt, NULL) != 0) > return -1; > assert(stmt != NULL); > + rmean_collect(rmean_box, IPROTO_PREPARE, 1); 1. Nikita is right, this is called when IPROTO_EXECUTE arrives. You can see that in iproto.cc. This is a separate question, why do we collect IPROTO_* statistics out of iproto. For now lets just use IPROTO_EXECUTE here. > enum sql_serialization_format format = sql_column_count(stmt) > 0 ? > DQL_EXECUTE : DML_EXECUTE; > port_sql_create(port, stmt, format, true); > diff --git a/test/box-tap/cfg.test.lua b/test/box-tap/cfg.test.lua > index d529447bb..d367aab07 100755 > --- a/test/box-tap/cfg.test.lua > +++ b/test/box-tap/cfg.test.lua > @@ -6,7 +6,7 @@ local socket = require('socket') > local fio = require('fio') > local uuid = require('uuid') > local msgpack = require('msgpack') > -test:plan(104) > +test:plan(106) 2. Here Nikita is also right. This file is for box.cfg() function tests. For iproto statistics, indeed, sql/iproto.test.lua would fit well.
next prev parent reply other threads:[~2020-02-13 21:44 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-10 18:35 Maria Khaydich 2020-02-10 23:06 ` Nikita Pettik 2020-02-13 21:44 ` Vladislav Shpilevoy [this message] 2020-02-19 16:37 ` Maria Khaydich 2020-02-19 17:16 ` Nikita Pettik 2020-02-25 11:08 ` Maria Khaydich 2020-02-25 13:02 ` Nikita Pettik 2020-02-25 20:29 ` Vladislav Shpilevoy 2020-02-26 15:50 ` Maria Khaydich 2020-02-27 0:08 ` Vladislav Shpilevoy 2020-02-27 13:21 ` Nikita Pettik 2020-03-03 16:42 ` Maria Khaydich 2020-03-03 22:39 ` Vladislav Shpilevoy 2020-03-06 11:34 ` Maria Khaydich 2020-03-06 14:32 ` Nikita Pettik 2020-03-06 15:09 ` Nikita Pettik 2020-03-04 13:47 ` Nikita Pettik 2020-02-25 22:26 ` Kirill Yukhin 2020-02-25 23:30 ` 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=d1d8fd96-340f-82b4-7d53-ebb86176928e@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=maria.khaydich@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH] box: sql prepare and execute statistics should be reflected in box.stat()' \ /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