首页 > 其他分享 >GBase 8a通过集群日志查看执行计划和每个阶段的整体耗时和各个节点的耗时做性能排查

GBase 8a通过集群日志查看执行计划和每个阶段的整体耗时和各个节点的耗时做性能排查

时间:2024-09-11 09:03:40浏览次数:9  
标签:11 10 09 18 8a 耗时 2020 54 GBase

GBase 8a提供了执行计划,以及不同的日志级别,现实整体各个节点耗时,以及每个节点的耗时,来方便用户进行性能排查,本文介绍详细的分析方法。

环境

2节点虚拟机集群

[gbase@rh6-1 ~]$ gcadmin
CLUSTER STATE:  ACTIVE
CLUSTER MODE:   NORMAL

=================================================================
|             GBASE COORDINATOR CLUSTER INFORMATION             |
=================================================================
|   NodeName   |     IpAddress     |gcware |gcluster |DataState |
-----------------------------------------------------------------
| coordinator1 |    10.0.2.201     | OPEN  |  OPEN   |    0     |
-----------------------------------------------------------------
=============================================================
|              GBASE DATA CLUSTER INFORMATION               |
=============================================================
|NodeName |     IpAddress     |gnode |syncserver |DataState |
-------------------------------------------------------------
|  node1  |    10.0.2.201     | OPEN |   OPEN    |    0     |
-------------------------------------------------------------
|  node2  |    10.0.2.202     | OPEN |   OPEN    |    0     |
-------------------------------------------------------------

简单的单列表,50万行

gbase> show create table t1;
+-------+-------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                                      |
+-------+-------------------------------------------------------------------------------------------------------------------+
| t1    | CREATE TABLE "t1" (
  "id" int(11) DEFAULT NULL
) ENGINE=EXPRESS DEFAULT CHARSET=utf8 TABLESPACE='sys_tablespace' |
+-------+-------------------------------------------------------------------------------------------------------------------+
1 row in set (Elapsed: 00:00:00.00)

gbase> select count(*) from t1;
+----------+
| count(*) |
+----------+
|   500000 |
+----------+
1 row in set (Elapsed: 00:00:00.06)

打开参数

其中profiling参数是可以直观的查看执行过程每个阶段的整体耗时。重点关注其中的Sending task to gnodes部分耗时。

gcluster_log_level参数7是可以查看到每个节点的具体SQL以及每个节点的耗时。

gbase> set profiling=1;
Query OK, 0 rows affected (Elapsed: 00:00:00.01)

gbase> set gcluster_log_level=7;
Query OK, 0 rows affected (Elapsed: 00:00:00.01)

执行计划

可以看到分成了3大部分。第0部分REDIST(id)是根据id列做重分布。第1部分[GATHER]是将各个节点的数据汇总,第2部分[RESULT]是返回结果。

gbase> explain select id,count(*) from t1 group by id order by count(*) desc limit 10;
+----+--------------+-----------+---------+-------------------------------------------------+-----------------+
| ID | MOTION       | OPERATION | TABLE   | CONDITION                                       | NO STAT Tab/Col |
+----+--------------+-----------+---------+-------------------------------------------------+-----------------+
| 02 | [RESULT]     |  Step     | <01>    |                                                 |                 |
|    |              |  ORDER    |         | ORDER BY cast(SUM_2ND(COUNT(0)) as signed) DESC |                 |
|    |              |  LIMIT    |         | LIMIT 10                                        |                 |
| 01 | [GATHER]     |  Step     | <00>    |                                                 |                 |
|    |              |  GROUP    |         | GROUP BY id                                     |                 |
|    |              |  ORDER    |         | ORDER BY .. DESC                                |                 |
|    |              |  LIMIT    |         | LIMIT 10                                        |                 |
| 00 | [REDIST(id)] |  Table    | t1[DIS] |                                                 | t1              |
|    |              |  GROUP    |         | GROUP BY id                                     |                 |
+----+--------------+-----------+---------+-------------------------------------------------+-----------------+
9 rows in set (Elapsed: 00:00:00.00)

执行SQL

包括profile的输出以及执行计划explain的结果。

gbase> select id,count(*) from t1 group by id order by count(*) desc limit 10;
+-------+----------+
| id    | count(*) |
+-------+----------+
| 27347 |       34 |
| 14427 |       32 |
| 27569 |       32 |
|  6983 |       32 |
| 32549 |       32 |
| 10186 |       32 |
| 25857 |       31 |
|  2197 |       31 |
| 23008 |       31 |
|  6582 |       31 |
+-------+----------+
10 rows in set (Elapsed: 00:00:00.77)

gbase> show profile;
+------------------------+----------+
| Status                 | Duration |
+------------------------+----------+
| parse                  | 0.000284 |
| init                   | 0.001421 |
| Preparing metadata     | 0.000495 |
| Executing by step      | 0.000550 |
| Creating tmp tables    | 0.000082 |
| Sending task to gnodes | 0.006993 |
| Sending task to gnodes | 0.666324 |
| Sending task to gnodes | 0.003851 |
| Creating tmp tables    | 0.000141 |
| Sending task to gnodes | 0.004463 |
| Sending task to gnodes | 0.068458 |
| Sending task to gnodes | 0.002863 |
| Sending task to gnodes | 0.011147 |
| Clearing tmp tables    | 0.000021 |
| Sending task to gnodes | 0.003134 |
| query end              | 0.000009 |
| freeing items          | 0.000113 |
| cleaning up            | 0.000003 |
+------------------------+----------+
18 rows in set (Elapsed: 00:00:00.00)

查看日志

查看gcluser/log/gcluster/express.log的对应输出。内部包含了整个执行过程以及每一步在每个节点的耗时情况。

先汇总一下后面详细日志的,方便查看

# 原始SQL
# 执行计划阶段
#0 第0步
##0-0 创建临时表
##0-1-1 创建临时表各个节点的执行时间
##0-2 将数据重分布到临时表
##0-2-1 重分布在各个节点的耗时
##0-3 刷新,因为重分布是底层操作,所以表一级要flush一下。
##0-3-1 刷新在各个节点耗时
#1 第1步
##1-1 在1个节点创建汇总临时表
##1-1-1 创建汇总临时表的耗时,注意只有1个
##1-2 汇总每个节点的结果到汇总表
##1-2-1 汇总耗时
##1-3 刷新汇总表
##1-3-1 刷新汇总表耗时
#2 第2步
##2-1 查询汇总表,得到结果
##2-1-1 查询汇总表耗时
#3 删除临时表,注意不同节点的SQL是不同的
#3-1 删除临时表耗时

原始日志

如下是express.log里面,日志等级为7的部分输出信息,其中[S:18]是对应的connection_id的编号18.

# 原始SQL
2020-11-10 09:54:16.382 [EXEC_P][INFO ][S:18][Q:38]:Original SQL:
select id,count(*) from t1 group by id order by count(*) desc limit 10
2020-11-10 09:54:16.382 [EXEC_P][INFO ][S:18][Q:38]:##############################
2020-11-10 09:54:16.382 [EXEC_P][INFO ][S:18][Q:38]:#### Main Query Begin ####
2020-11-10 09:54:16.382 [EXEC_P][INFO ][S:18][Q:38]:##############################

# 执行计划阶段
2020-11-10 09:54:16.382 [EXEC_P][INFO ][S:18][Q:38]:---Top plan is [0x5149de0]---

2020-11-10 09:54:16.382 [EXECTR][INFO ][S:18][Q:38]:Involved in 1 distribuitons
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:===========Datacopymap Of Distribution 2===========
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:|| n1 | ::ffff:10.0.2.202, ::ffff:10.0.2.201, ||
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:|| n2 | ::ffff:10.0.2.201, ::ffff:10.0.2.202, ||
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:===================================================
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Selected a random coordinator node: 10.0.2.201
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Coordinator node is 10.0.2.201
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:--#--Begin a async API mode--#--
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:A plan Begin ...
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 0 scalar subquery.
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 0 from subquery.
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 0 union subquery.
2020-11-10 09:54:16.383 [EXEC_P][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 3 steps.


#0 第0步
2020-11-10 09:54:16.383 [EXEC_P][INFO ][S:18][Q:38]:## STEP: 0 ...

2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 0 uncorrelated subquery.
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:Distribution Info, /[8a:P2C2]
##0-0 创建临时表
2020-11-10 09:54:16.383 [EXECTR][INFO ][S:18][Q:38]:---Step detail: hash redistribute the table in gbase.
2020-11-10 09:54:16.384 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

2020-11-10 09:54:16.385 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.202:5050->33) , SQL:CREATE TABLE `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n1 AS SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `testdb.t1`.`id` AS `c2`, COUNT(0) AS `c3` FROM `testdb`.`t1_n1` `testdb.t1` GROUP BY `testdb.t1`.`id` LIMIT 0 ; commit.
2020-11-10 09:54:16.385 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:CREATE TABLE `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n2 AS SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `testdb.t1`.`id` AS `c2`, COUNT(0) AS `c3` FROM `testdb`.`t1_n2` `testdb.t1` GROUP BY `testdb.t1`.`id` LIMIT 0 ; commit.

##0-1-1 创建临时表各个节点的执行时间
2020-11-10 09:54:16.393 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.202 | 5050 | 0         s | Finish   |
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+

2020-11-10 09:54:16.394 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

##0-2 将数据重分布到临时表
2020-11-10 09:54:16.397 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.202:5050->33) , SQL:SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `testdb.t1`.`id` AS `c2`, COUNT(0) AS `c3` FROM `testdb`.`t1_n1` `testdb.t1` GROUP BY `testdb.t1`.`id` target into server (HOST '::ffff:10.0.2.202,::ffff:10.0.2.201', PORT 5050, USER 'root', PASSWORD '', DATABASE 'gctmpdb', TABLE '_tmp_rht_3372351498_18_t2_1_1604972970_s_n1,_tmp_rht_3372351498_18_t2_1_1604972970_s_n2', COMMENT 'group 0, distribution 2, hash_map 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2020-11-10 09:54:16.400 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `testdb.t1`.`id` AS `c2`, COUNT(0) AS `c3` FROM `testdb`.`t1_n2` `testdb.t1` GROUP BY `testdb.t1`.`id` target into server (HOST '::ffff:10.0.2.202,::ffff:10.0.2.201', PORT 5050, USER 'root', PASSWORD '', DATABASE 'gctmpdb', TABLE '_tmp_rht_3372351498_18_t2_1_1604972970_s_n1,_tmp_rht_3372351498_18_t2_1_1604972970_s_n2', COMMENT 'group 0, distribution 2, hash_map 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

##0-2-1 重分布在各个节点的耗时
2020-11-10 09:54:17.140 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.201 | 5050 | 1         s | Finish   |
|  T   | ::ffff:10.0.2.202 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+

2020-11-10 09:54:17.140 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

##0-3 刷新,因为重分布是底层操作,所以表一级要flush一下。
2020-11-10 09:54:17.141 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.202:5050->33) , SQL:flush temporary commit `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n1.
2020-11-10 09:54:17.141 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:flush temporary commit `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n2.

##0-3-1 刷新在各个节点耗时
2020-11-10 09:54:17.144 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.202 | 5050 | 0         s | Finish   |
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+

#1 第1步
2020-11-10 09:54:17.144 [EXEC_P][INFO ][S:18][Q:38]:## STEP: 1 ...

2020-11-10 09:54:17.144 [EXECTR][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 0 uncorrelated subquery.
2020-11-10 09:54:17.144 [EXECTR][INFO ][S:18][Q:38]:Distribution Info, [Coor:C2]/[8a:P2]
2020-11-10 09:54:17.144 [EXECTR][INFO ][S:18][Q:38]:---Step detail: 8a to cluster, gbase8a is producer and gcluster is consumer, the query result is store in gcluster.
2020-11-10 09:54:17.145 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

##1-1 在1个节点创建汇总临时表
2020-11-10 09:54:17.145 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:CREATE TABLE `gctmpdb`._tmp_3372351498_18_t2_2_1604972970_s AS SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `_tmp_rht_3372351498_18_t2_1_1604972970_s_n2`.`c2` AS `c4`, cast(SUM_2ND(`_tmp_rht_3372351498_18_t2_1_1604972970_s_n2`.`c3`) as signed) AS `c5` FROM `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n2 GROUP BY `_tmp_rht_3372351498_18_t2_1_1604972970_s_n2`.`c2` LIMIT 0 ; commit.

##1-1-1 创建汇总临时表的耗时,注意只有1个
2020-11-10 09:54:17.181 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+

2020-11-10 09:54:17.181 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

##1-2 汇总每个节点的结果到汇总表
2020-11-10 09:54:17.181 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.202:5050->33) , SQL:SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `_tmp_rht_3372351498_18_t2_1_1604972970_s_n1`.`c2` AS `c4`, cast(SUM_2ND(`_tmp_rht_3372351498_18_t2_1_1604972970_s_n1`.`c3`) as signed) AS `c5` FROM `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n1 GROUP BY `_tmp_rht_3372351498_18_t2_1_1604972970_s_n1`.`c2` ORDER BY `c5` DESC LIMIT 10 target into server (HOST '::ffff:10.0.2.201', PORT 5050, USER 'root', PASSWORD '', DATABASE 'gctmpdb', TABLE '_tmp_3372351498_18_t2_2_1604972970_s', COMMENT '' ).
2020-11-10 09:54:17.181 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `_tmp_rht_3372351498_18_t2_1_1604972970_s_n2`.`c2` AS `c4`, cast(SUM_2ND(`_tmp_rht_3372351498_18_t2_1_1604972970_s_n2`.`c3`) as signed) AS `c5` FROM `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n2 GROUP BY `_tmp_rht_3372351498_18_t2_1_1604972970_s_n2`.`c2` ORDER BY `c5` DESC LIMIT 10 target into server (HOST '::ffff:10.0.2.201', PORT 5050, USER 'root', PASSWORD '', DATABASE 'gctmpdb', TABLE '_tmp_3372351498_18_t2_2_1604972970_s', COMMENT '' ).

##1-2-1 汇总耗时
2020-11-10 09:54:17.270 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
|  T   | ::ffff:10.0.2.202 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+

2020-11-10 09:54:17.271 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

##1-3 刷新汇总表
2020-11-10 09:54:17.271 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:flush temporary commit `gctmpdb`._tmp_3372351498_18_t2_2_1604972970_s.

##1-3-1 刷新汇总表耗时
2020-11-10 09:54:17.272 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+


#2 第2步
2020-11-10 09:54:17.272 [EXEC_P][INFO ][S:18][Q:38]:## STEP: 2 ...

2020-11-10 09:54:17.272 [EXECTR][INFO ][S:18][Q:38]:Current plan [0x5149de0] has 0 uncorrelated subquery.
2020-11-10 09:54:17.272 [EXECTR][INFO ][S:18][Q:38]:Distribution Info, [Coor:P2]
2020-11-10 09:54:17.272 [EXECTR][INFO ][S:18][Q:38]:---Step detail: cluster to client, gcluster is procducer and send the query result to client.
2020-11-10 09:54:17.272 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!

##2-1 查询汇总表,得到结果
2020-11-10 09:54:17.273 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->10) , SQL:SELECT /*::ffff:10.0.2.201_18_4_2020-11-10_09:54:16*/ /*+ TID('2621458') */ `_tmp_3372351498_18_t2_2_1604972970_s`.`c4` AS `id`, `_tmp_3372351498_18_t2_2_1604972970_s`.`c5` AS `count(*)` FROM `gctmpdb`._tmp_3372351498_18_t2_2_1604972970_s ORDER BY `count(*)` DESC LIMIT 10.
2020-11-10 09:54:17.274 [EXECTR][INFO ][S:18][Q:38]:Sent Rows: 10

##2-1-1 查询汇总表耗时
2020-11-10 09:54:17.274 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+

2020-11-10 09:54:17.274 [EXECTR][INFO ][S:18][Q:38]:Finish all steps of plan [0x5149de0].

2020-11-10 09:54:17.274 [EXECTR][INFO ][S:18][Q:38]:Passed tasks to async API, good luck!


#3 删除临时表,注意不同节点的SQL是不同的
2020-11-10 09:54:17.276 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.201:5050->24) , SQL:DROP TABLE IF EXISTS `gctmpdb`._tmp_3372351498_18_t2_2_1604972970_s;DROP TABLE IF EXISTS `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n2.
2020-11-10 09:54:17.278 [SQLDISP][INFO ][S:18][Q:38]:Target:HOST(::ffff:10.0.2.202:5050->42) , SQL:DROP TABLE IF EXISTS `gctmpdb`._tmp_rht_3372351498_18_t2_1_1604972970_s_n1.

#3-1 删除临时表耗时
2020-11-10 09:54:17.279 [EXECTR][INFO ][S:18][Q:38]:
-----------------+----Node Performance----+---------------
+-Type-+-------Node------+-Port-+---Elapsed---+--Status--+
|  T   | ::ffff:10.0.2.202 | 5050 | 0         s | Finish   |
|  T   | ::ffff:10.0.2.201 | 5050 | 0         s | Finish   |
+------+-----------------+------+-------------+----------+
来源:https://www.gbase8.cn/1953

标签:11,10,09,18,8a,耗时,2020,54,GBase
From: https://www.cnblogs.com/shujuyr/p/18407632

相关文章

  • kingbase——创建timestampdiff函数
    创建函数如下:CREATEORREPLACEFUNCTION"ops_data"."timestampdiff"("para1"text,"para2""sys"."timestamp","para3""sys"."timestamp")RETURNS"pg_catalog".&q......
  • javase复习day18API
    游戏打包exeMathabs方法的小bug:以int类型为例,取值范围:-2147483648~2147483647如果没有正数与之对应,那么传递负数结果有误-2147483648没有正数对应则结果还是 -2147483648可以使用JDK15后的新方法absExact如果结果有误则会报错packageMathDemo1;publiccla......
  • jsp仓储管理系统9e8ai 本系统(程序+源码+数据库+调试部署+开发环境)带论文文档1万字以上
    jsp仓储管理系统9e8ai本系统(程序+源码+数据库+调试部署+开发环境)带论文文档1万字以上,文末可获取,系统界面在最后面。系统程序文件列表项目功能客户,库存人员,入库人员,出库人员,商品类别,商品信息,仓区信息,商品入库,商品出库开题报告内容一、项目背景与意义随着电子商......
  • Springboot计算机毕业设计网上电影购票系统8a3i3
    本系统(程序+源码+数据库+调试部署+开发环境)带论文文档1万字以上,文末可获取,系统界面在最后面。系统程序文件列表用户,影院信息,电影类型,热门电影,电影排期,最新电影,票房榜单开题报告内容一、课题名称网上电影购票系统设计和实现二、设计(论文)教学目标通过本课题的设计,旨......
  • kingbase——创建truncate函数
    写上一篇比较round函数与truncate函数时,顺手试了一下KINGBASE数据库,应该是没有TRUNCATE这个函数,要使用估计得手动创建。创建函数如下createorreplacefunctionsys.truncate(numeric,int4)returnsnumericasdeclarevaluenumeric;resultnumeric;beginva......
  • TensorRT量化模型分析(耗时分布可视化等)
    文章目录TensorRT量化模型分析一背景二准备工作1.代码准备2.依赖环境三分析过程1.导出模型2.模型形态比对3.转tensorrt序列化文件4.tensorrt序列化文件(即tensorrt模型)分析四其他TIPSTensorRT量化模型分析一背景​在TensorRT模型量化......
  • 使用Golang的协程竟然变慢了|100万个协程的归并排序耗时分析
    前言这篇文章将用三个版本的归并排序,为大家分析使用协程排序的时间开销(被排序的切片长度由128到1000w)本期demo地址:https://github.com/BaiZe1998/go-learning往期视频讲解......
  • 分析ueventd Coldboot耗时问题
    安卓go平台启动时间发现如下ueventd耗时1.907s问题:01-1100:20:02.85400Iinit:Parsingfile/odm/etc/init...01-1100:20:02.85400Einit:Unabletoopen'/odm/etc/init':Nosuchfileordirectory01-1100:20:02.85400Iinit......
  • KingbaseES RAC 部署案例之---单节点部署案例
    案例说明:KingbaseESRAC在单节点上部署。适用版本:KingbaseESV008R006C008M030B0010操作系统:[root@node201KingbaseHA]#cat/etc/centos-releaseCentOSLinuxrelease7.9.2009(Core)集群节点信息:[root@node203~]#cat/etc/hosts.......192.168.1.203node203......
  • 直播系统开发,接口异步调用一小步,耗时减少一大步
    直播系统开发,接口异步调用一小步,耗时减少一大步随着直播系统开发业务发展,底层数据量越来越大,业务逻辑也日趋复杂化,某些接口耗时也越来越长,这时候接口就需要进行性能优化了,当然性能优化主要跟业务相关涉及改造点可能各不相同,这里就来介绍异步调用多个接口减少响应时间。适用......