实践练习六（必选）：查看 OceanBase 执行计划

最新推荐文章于 2024-05-08 20:13:12 发布
最新推荐文章于 2024-05-08 20:13:12 发布
阅读量404 收藏
点赞数
文章标签： oceanbase
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/redgame7/article/details/128873122
版权

使用 BenmarkSQL 运行 TPC-C
下载BenmarkSQL

[root@cts07 ~]# yum install git -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.aliyun.com
 * extras: mirrors.aliyun.com
 * updates: mirrors.aliyun.com
Package git-1.8.3.1-23.el7_8.x86_64 already installed and latest version
Nothing to do

下载benchmarksql

[root@cts07 ~]# git clone https://github.com/obpilot/benchmarksql-5.0.git
Cloning into 'benchmarksql-5.0'...
remote: Enumerating objects: 110, done.
remote: Counting objects: 100% (110/110), done.
remote: Compressing objects: 100% (90/90), done.
remote: Total 110 (delta 14), reused 105 (delta 12), pack-reused 0
Receiving objects: 100% (110/110), 5.58 MiB | 4.98 MiB/s, done.
Resolving deltas: 100% (14/14), done.

编辑props.ob配置文件
这个配置文件在/root/benchmarksql-5.0/run/目录下，编辑后的内容如下：

db=oracle

driver=com.alipay.oceanbase.obproxy.mysql.jdbc.Driver
//driver=com.alipay.oceanbase.jdbc.Driver
conn=jdbc:oceanbase://127.0.0.1:2883/obtest?useUnicode=true&characterEncoding=utf-8
user=root@sys#obdemo
password=root123

warehouses=2
loadWorkers=2

terminals=2
//To run specified transactions per terminal- runMins must equal zero
runTxnsPerTerminal=0
//To run for specified minutes- runTxnsPerTerminal must equal zero
runMins=1
//Number of total transactions per minute
limitTxnsPerMin=0

//Set to true to run in 4.x compatible mode. Set to false to use the
//entire configured database evenly.
terminalWarehouseFixed=true

//The following five values must add up to 100
newOrderWeight=45
paymentWeight=43
orderStatusWeight=4
deliveryWeight=4
stockLevelWeight=4

// Directory name to create for collecting detailed result data.
// Comment this out to suppress.
resultDirectory=my_result_%tY-%tm-%td_%tH%tM%tS
osCollectorScript=./misc/os_collector_linux.py
osCollectorInterval=1

运行创建表语句

编辑一下runSQL.sh文件，更改内容如下：

#!/usr/bin/env bash
if [ $# -ne 2 ] ; then
    echo "usage: $(basename $0) PROPS_FILE SQL_FILE" >&2
    exit 2
fi

source /root/benchmarksql-5.0/run/funcs.sh $1 

[admin@cts07 run]$ obclient -h 192.168.1.246 -P 2883 -uroot@sys#obdemo -proot123 -c -A oceanbase
MySQL [oceanbase]> create database obtest;


执行脚本

[admin@cts07 run]$ sh runSQL.sh props.ob sql.common/tableCreates.sql
# ------------------------------------------------------------
# Loading SQL file sql.common/tableCreates.sql
# ------------------------------------------------------------
create table bmsql_config (
cfg_name    varchar(30) primary key,
cfg_value   varchar(50)
);
create table bmsql_warehouse (
w_id        integer   not null,
w_ytd       decimal(12,2),
w_tax       decimal(4,4),
w_name      varchar(10),
w_street_1  varchar(20),
w_street_2  varchar(20),
w_city      varchar(20),
w_state     char(2),
w_zip       char(9)
);
create table bmsql_district (
d_w_id       integer       not null,
d_id         integer       not null,
d_ytd        decimal(12,2),
d_tax        decimal(4,4),
d_next_o_id  integer,
d_name       varchar(10),
d_street_1   varchar(20),
d_street_2   varchar(20),
d_city       varchar(20),
d_state      char(2),
d_zip        char(9)
);

数据装载
装载前先优化一下测试租户的设置，避免大事务超时，先登陆到租户

obclient -h 192.168.1.246 -P 2883 -uroot@sys#obdemo -proot123 -c -A oceanbase

设置以下租户全局变量：

set global ob_timestamp_service='GTS' ;
set global autocommit=ON;
set global ob_query_timeout=36000000000;
set global ob_trx_timeout=36000000000;
set global max_allowed_packet=67108864;
set global ob_sql_work_area_percentage=100;
set global parallel_max_servers=800;
set global parallel_servers_target=800;

运行脚本，装载数据，输出显示装载成功，仓库数选的小一些

[admin@cts07 run]$ cat runLoader.sh
#!/usr/bin/env bash

if [ $# -lt 1 ] ; then
    echo "usage: $(basename $0) PROPS_FILE [ARGS]" >&2
    exit 2
fi

source /home/admin/benchmarksql-5.0/run/funcs.sh $1
shift

setCP || exit 1

java -cp "$myCP" -Dprop=$PROPS LoadData $*

[admin@cts07 run]$ sh runLoader.sh props.ob
Starting BenchmarkSQL LoadData

driver=com.alipay.oceanbase.obproxy.mysql.jdbc.Driver
conn=jdbc:oceanbase://127.0.0.1:2883/obtest?useUnicode=true&characterEncoding=utf-8
user=root@sys#obdemo
password=***********
warehouses=2
loadWorkers=2
fileLocation (not defined)
csvNullValue (not defined - using default 'NULL')

Worker 000: Loading ITEM
Worker 000: ERROR: Duplicate entry 'warehouses' for key 'PRIMARY'
Worker 001: Loading Warehouse      1
Worker 001: Loading Warehouse      1 done
Worker 001: Loading Warehouse      2
Worker 001: Loading Warehouse      2 done

登陆到数据库，创建两个索引

[admin@cts07 ~]$ obclient -h192.168.1.246 -uroot@sys#obdemo -P2883 -proot123 -c -A oceanbase
MySQL [test]> use obtest
Database changed

MySQL [obtest]> create index bmsql_customer_idx1 on bmsql_customer (c_w_id, c_d_id, c_last, c_first) local;
Query OK, 0 rows affected (6.957 sec)

MySQL [obtest]> create index bmsql_oorder_idx1 on bmsql_oorder (o_w_id, o_d_id, o_carrier_id, o_id) local;
Query OK, 0 rows affected (4.558 sec)

运行TPCC测试

[admin@cts07 run]$ sh runBenchmark.sh props.ob
23:58:34,605 [main] INFO   jTPCC : Term-00,
23:58:34,635 [main] INFO   jTPCC : Term-00, +-------------------------------------------------------------+
23:58:34,635 [main] INFO   jTPCC : Term-00,      BenchmarkSQL v5.0
23:58:34,636 [main] INFO   jTPCC : Term-00, +-------------------------------------------------------------+
23:58:34,636 [main] INFO   jTPCC : Term-00,  (c) 2003, Raul Barbosa
23:58:34,636 [main] INFO   jTPCC : Term-00,  (c) 2004-2016, Denis Lussier
23:58:34,645 [main] INFO   jTPCC : Term-00,  (c) 2016, Jan Wieck
23:58:34,645 [main] INFO   jTPCC : Term-00, +-------------------------------------------------------------+
23:58:34,645 [main] INFO   jTPCC : Term-00,
23:58:34,646 [main] INFO   jTPCC : Term-00, db=oracle
23:58:34,656 [main] INFO   jTPCC : Term-00, driver=com.alipay.oceanbase.obproxy.mysql.jdbc.Driver
23:58:34,671 [main] INFO   jTPCC : Term-00, conn=jdbc:oceanbase://127.0.0.1:2883/obtest?useUnicode=true&characterEncoding=utf-8
23:58:34,671 [main] INFO   jTPCC : Term-00, user=root@sys#obdemo
23:58:34,678 [main] INFO   jTPCC : Term-00,
23:58:34,691 [main] INFO   jTPCC : Term-00, warehouses=2
23:58:34,691 [main] INFO   jTPCC : Term-00, terminals=2
23:58:34,701 [main] INFO   jTPCC : Term-00, runMins=1
23:58:34,702 [main] INFO   jTPCC : Term-00, limitTxnsPerMin=0
23:58:34,703 [main] INFO   jTPCC : Term-00, terminalWarehouseFixed=true
23:58:34,703 [main] INFO   jTPCC : Term-00,
23:58:34,703 [main] INFO   jTPCC : Term-00, newOrderWeight=45
23:58:34,704 [main] INFO   jTPCC : Term-00, paymentWeight=43
23:58:34,704 [main] INFO   jTPCC : Term-00, orderStatusWeight=4
23:58:34,704 [main] INFO   jTPCC : Term-00, deliveryWeight=4
23:58:34,704 [main] INFO   jTPCC : Term-00, stockLevelWeight=4
23:58:34,705 [main] INFO   jTPCC : Term-00,
23:58:34,705 [main] INFO   jTPCC : Term-00, resultDirectory=my_result_%tY-%tm-%td_%tH%tM%tS
23:58:34,705 [main] INFO   jTPCC : Term-00, osCollectorScript=./misc/os_collector_linux.py
23:58:34,707 [main] INFO   jTPCC : Term-00,
23:58:34,850 [main] INFO   jTPCC : Term-00, copied props.ob to my_result_2023-02-06_235834/run.properties
23:58:34,852 [main] INFO   jTPCC : Term-00, created my_result_2023-02-06_235834/data/runInfo.csv for runID 7
23:58:34,854 [main] INFO   jTPCC : Term-00, writing per transaction results to my_result_2023-02-06_235834/data/result.csv
23:58:34,857 [main] INFO   jTPCC : Term-00, osCollectorScript=./misc/os_collector_linux.py
23:58:34,858 [main] INFO   jTPCC : Term-00, osCollectorInterval=1
23:58:34,858 [main] INFO   jTPCC : Term-00, osCollectorSSHAddr=null
23:58:34,858 [main] INFO   jTPCC : Term-00, osCollectorDevices=null
23:58:35,280 [main] INFO   jTPCC : Term-00,
23:58:36,417 [main] INFO   jTPCC : Term-00, C value for C_LAST during load: 207
23:58:36,417 [main] INFO   jTPCC : Term-00, C value for C_LAST this run:    103
23:58:36,417 [main] INFO   jTPCC : Term-00,                                                                                                                                                       Term00:02:47,571 [Thread-1] INFO   jTPCC : Term-00, pmTOTAL: 36    Memory Usage: 22MB / 299MB
00:02:47,572 [Thread-1] INFO   jTPCC : Term-00,
00:02:47,572 [Thread-1] INFO   jTPCC : Term-00, Measured tpmC (NewOrders) = 0.47
00:02:47,572 [Thread-1] INFO   jTPCC : Term-00, Measured tpmTOTAL = 0.95
00:02:47,572 [Thread-1] INFO   jTPCC : Term-00, Session Start     = 2023-02-06 23:58:36
00:02:47,572 [Thread-1] INFO   jTPCC : Term-00, Session End       = 2023-02-07 00:02:47
00:02:47,572 [Thread-1] INFO   jTPCC : Term-00, Transaction Count = 3

TPC-C TOP SQL分析

查询TOP SQL

MySQL [obtest]> SELECT /*+ PARALLEL(15)*/ avg_exe_usec,
    ->         tenant_id,
    ->         plan_id,
    ->          svr_ip,
    ->          svr_port,
    ->          sql_id,
    ->         db_id,
    ->         query_sql
    -> FROM oceanbase.gv$plan_cache_plan_stat
    -> WHERE db_id='18446744073709551615'
    -> ORDER BY  avg_exe_usec DESC LIMIT 3;
+--------------+-----------+---------+---------------+----------+----------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| avg_exe_usec | tenant_id | plan_id | svr_ip        | svr_port | sql_id                           | db_id                | query_sql                                                                                                                                                                                                                                                  |
+--------------+-----------+---------+---------------+----------+----------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|     18720981 |         1 |     840 | 192.168.1.246 |     2882 | 7229213613983BC5FDA15AD11EC70D01 | 18446744073709551615 | SELECT s_quantity, s_data,        s_dist_01, s_dist_02, s_dist_03, s_dist_04,        s_dist_05, s_dist_06, s_dist_07, s_dist_08,        s_dist_09, s_dist_10     FROM bmsql_stock     WHERE s_w_id = 1 AND s_i_id = 23452     FOR UPDATE                   |
|      9012268 |         1 |     843 | 192.168.1.246 |     2882 | E1F2BDA1D7391B757859ED3704E5AFB7 | 18446744073709551615 | UPDATE bmsql_stock     SET s_quantity = 30, s_ytd = s_ytd + 7,         s_order_cnt = s_order_cnt + 1,         s_remote_cnt = s_remote_cnt + 0     WHERE s_w_id = 1 AND s_i_id = 23452                                                                      |
|      6550077 |         1 |     835 | 192.168.1.246 |     2882 | AE32C84F890055A535A28B262C649D41 | 18446744073709551615 | SELECT c_first, c_middle, c_last, c_street_1, c_street_2,        c_city, c_state, c_zip, c_phone, c_since, c_credit,        c_credit_lim, c_discount, c_balance     FROM bmsql_customer     WHERE c_w_id = 1 AND c_d_id = 2 AND c_id = 2714     FOR UPDATE |
+--------------+-----------+---------+---------------+----------+----------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
3 rows in set (0.332 sec)

执行SQL、查看执行计划


MySQL [obtest]> SELECT sum(ol_amount) AS sum_ol_amount
    -> FROM bmsql_order_line
    -> WHERE ol_w_id = 2
    ->         AND ol_d_id = 4
    ->         AND ol_o_id = 2119;
+---------------+
| sum_ol_amount |
+---------------+
|      49386.24 |
+---------------+
1 row in set (13.310 sec)

MySQL [obtest]> SELECT s_quantity,
    ->          s_data,
    ->          s_dist_01,
    ->          s_dist_02,
    ->          s_dist_03,
    ->          s_dist_04,
    ->          s_dist_05,
    ->          s_dist_06,
    ->          s_dist_07,
    ->          s_dist_08,
    ->          s_dist_09,
    ->          s_dist_10
    -> FROM bmsql_stock
    -> WHERE s_w_id = 1
    ->         AND s_i_id = 44448 FOR UPDATE;
+------------+--------------------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+
| s_quantity | s_data                               | s_dist_01                | s_dist_02                | s_dist_03                | s_dist_04                | s_dist_05                | s_dist_06                | s_dist_07                | s_dist_08                | s_dist_09                | s_dist_10                |
+------------+--------------------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+
|         83 | c77MWxweZFU360RunLE8rzvOOir6fL0NbLSq | fY0NVkYOnuLnqoIdpGAi2MXw | LLzRFwgnQFuSHsbRg5LqAvs6 | WbBbq3Ua3ajw7UcBdWKk7SXR | n37B93xHYoYRBMgOz7s68JPq | aGFeUB0tLhtmmSMgB0RfpHtp | drrXTcXM8Hkjtor1Jv0M7Hg8 | Kw38MKJGb4rwt4oFddT24OWH | TGJ2mQwdwrolCQ2pqLEBmFog | oG2BEZL03Gks9KLqwa8y3CYk | V1hGJiFeQtSlnC7K0AzQxD3K |
|         32 | qUG76KNPwKkR9rzZGdlxb53qAN0CcrYd     | zuLQIEbj8tTxaak5lnH3DA2Q | eXe2QshAQgyS7UyBqachNOYg | XgjQie2Ked0FO3GZiQZbJc7W | hAH6lMRh2QOJ3AX5U28xa5W3 | nHcy5pWeLRxpUkYCkkoF2Agn | Pbg7XvTNtkA9eJGyHseW3HJa | ZEU63NG6vEEMrCphxXdQleQA | YehPtGraIRVjzIhdpLXqgoC0 | VuK07QbUFhfPknlI2DmBxFVM | HaQNwmgZCKDERCTSxt4DE226 |
+------------+--------------------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+--------------------------+
2 rows in set (20.373 sec)

MySQL [obtest]> UPDATE bmsql_stock SET s_quantity = 50,
    ->          s_ytd = s_ytd + 1,
    ->          s_order_cnt = s_order_cnt + 1,
    ->          s_remote_cnt = s_remote_cnt + 0
    -> WHERE s_w_id = 2
    ->         AND s_i_id = 12177;
Query OK, 1 row affected (9.229 sec)
Rows matched: 1  Changed: 1  Warnings: 0

MySQL [obtest]> SELECT sum(ol_amount) AS sum_ol_amount
    -> FROM bmsql_order_line
    -> WHERE ol_w_id = 2
    ->         AND ol_d_id = 4
    ->         AND ol_o_id = 2119;
+---------------+
| sum_ol_amount |
+---------------+
|      49386.24 |
+---------------+
1 row in set (9.690 sec)

MySQL [obtest]> explain SELECT c_data
    -> FROM bmsql_customer
    -> WHERE c_w_id = 1
    ->         AND c_d_id = 9
    ->         AND c_id = 511;\G
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Query Plan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| ===================================================================
|ID|OPERATOR  |NAME                               |EST. ROWS|COST |
-------------------------------------------------------------------
|0 |TABLE SCAN|bmsql_customer(bmsql_customer_idx1)|60       |35479|
===================================================================

Outputs & filters:
-------------------------------------
  0 - output([bmsql_customer.c_data]), filter([bmsql_customer.c_id = 511]),
      access([bmsql_customer.c_id], [bmsql_customer.c_data]), partitions(p0)
 |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.134 sec)

MySQL [obtest]> explain UPDATE bmsql_district SET d_ytd = d_ytd + 479.86
    -> WHERE d_w_id = 1
    ->         AND d_id = 10\G;
*************************** 1. row ***************************
Query Plan: ==============================================
|ID|OPERATOR   |NAME          |EST. ROWS|COST|
----------------------------------------------
|0 |UPDATE     |              |1        |64  |
|1 | TABLE SCAN|bmsql_district|1        |64  |
==============================================

Outputs & filters:
-------------------------------------
  0 - output(nil), filter(nil), table_columns([{bmsql_district: ({bmsql_district: (bmsql_district.__pk_increment, bmsql_district.d_w_id, bmsql_district.d_id, bmsql_district.d_ytd, bmsql_district.d_tax, bmsql_district.d_next_o_id, bmsql_district.d_name, bmsql_district.d_street_1, bmsql_district.d_street_2, bmsql_district.d_city, bmsql_district.d_state, bmsql_district.d_zip)})}]),
      update([bmsql_district.d_ytd=column_conv(DECIMAL,PS:(12,2),NULL,bmsql_district.d_ytd + 479.86)])
  1 - output([bmsql_district.__pk_increment], [bmsql_district.d_w_id], [bmsql_district.d_id], [bmsql_district.d_ytd], [bmsql_district.d_tax], [bmsql_district.d_next_o_id], [bmsql_district.d_name], [bmsql_district.d_street_1], [bmsql_district.d_street_2], [bmsql_district.d_city], [bmsql_district.d_state], [bmsql_district.d_zip], [column_conv(DECIMAL,PS:(12,2),NULL,bmsql_district.d_ytd + 479.86)]), filter([bmsql_district.d_w_id = 1], [bmsql_district.d_id = 10]),
      access([bmsql_district.d_ytd], [bmsql_district.__pk_increment], [bmsql_district.d_w_id], [bmsql_district.d_id], [bmsql_district.d_tax], [bmsql_district.d_next_o_id], [bmsql_district.d_name], [bmsql_district.d_street_1], [bmsql_district.d_street_2], [bmsql_district.d_city], [bmsql_district.d_state], [bmsql_district.d_zip]), partitions(p0)

1 row in set (0.072 sec)

MySQL [obtest]> explain SELECT d_name,
    ->          d_street_1,
    ->          d_street_2,
    ->          d_city,
    ->          d_state,
    ->          d_zip
    -> FROM bmsql_district
    -> WHERE d_w_id = 1
    ->         AND d_id = 10\G;
*************************** 1. row ***************************
Query Plan: =============================================
|ID|OPERATOR  |NAME          |EST. ROWS|COST|
---------------------------------------------
|0 |TABLE SCAN|bmsql_district|1        |62  |
=============================================

Outputs & filters:
-------------------------------------
  0 - output([bmsql_district.d_name], [bmsql_district.d_street_1], [bmsql_district.d_street_2], [bmsql_district.d_city], [bmsql_district.d_state], [bmsql_district.d_zip]), filter([bmsql_district.d_w_id = 1], [bmsql_district.d_id = 10]),
      access([bmsql_district.d_w_id], [bmsql_district.d_id], [bmsql_district.d_name], [bmsql_district.d_street_1], [bmsql_district.d_street_2], [bmsql_district.d_city], [bmsql_district.d_state], [bmsql_district.d_zip]), partitions(p0)

1 row in set (0.050 sec)

ERROR: No query specified

redgame7
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
OceanBase实践练习六
03-15
OceanBase实践练习六
OceanBase实践练习一
03-15
OceanBase实践练习一 OceanBase是一个分布式关系数据库管理系统，它提供了高性能、可扩展性强和高可用性的数据库解决方案。下面是一个OceanBase实践练习的一些重要知识点总结： 1.OceanBase集群部署 OceanBase...
【OceanBase 系列】—— OceanBase v4.3 特性解读：查询性能提升之利器列存储引擎
最新发布
汤庆
05-08 1346
对于分析类查询，列存可以极大地提升查询性能，也是 OceanBase 做好 HTAP 和 OLAP 的一项不可缺少的特性。本文介绍 OceanBase 列存的实现特色。
基于Benchmark查看OceanBase执行计划
IT邦德
03-16 2204
本文详细介绍了OceanBase 的执行计划查看方法，包括 explain 命令和查看实际执行计划。
【OceanBase】分布式事务高级技术
weixin_43346403的博客
02-25 479
8.OceanBase通过多种机制保证分布式事务跨机执行的ACID。2.快照隔离级别（snapshot isolation）6.OceanBase全局一致性快照技术。11.OceanBase两阶段提交协议。3.OceanBase的隔离级别。1.全局快照及分布式一致性读。13.OB两阶段提交延迟分析。4.分布式数据库面临的挑战。5.业界常用解决方案。7.GTS服务高可用。9.分布式两阶段提交。12.OB两阶段提交。14.分布式事务优化。
OceanBase 4.2特性解读：Show Trace全链路跟踪，助力快速问题定位与精准诊断
OceanBase分布式数据库的博客
01-13 1186
最后，用户可以在 OceanBase 新版本的交互场景使用 Show Trace 能力，用户在命令行中手动执行某一个语句后，如果想分析该语句的执行调用链路情况，以及链路中各阶段耗时情况，以便进行性能分析或调优，可以使用 Show Trace 功能便捷地找到性能瓶颈点。用户通过 OCP，可以通过不同维度快速检索到有问题的请求，比如按耗时检索, 按指定 Trace id 或者 SQL ID 检索等, 并且直观的看到请求从客户端到数据库内部全链路各组件的执行信息, 方便快速定位出问题的阶段。
OceanBase由于合并操作导致事务被杀死的情况。
weixin_34119545的博客
10-04 236
OceanBase是一台内存数据库，兼容MySQL协议以及SQL协议，拥有跟内存数据库一样的属性：所有的数据都需要先写入到内存里面，但是并不会立刻落盘写入到存储里面，需要等一次合并操作，将内存里面所有的改动落盘到存储里面。所以发生这种合并操作的时候，伴随着资源的使用，也会出现问题。我们来看其中一种由于合并操作导致数据库杀死事务的情况如何排查...
OceanBase查询优化器和执行计划
互联网知识分享
08-21 642
查询优化器是数据库系统中的一个重要组件，负责对SQL语句进行优化，生成最优的执行计划。在OceanBase中，查询优化器扮演着至关重要的角色，它能够通过一系列的优化算法和规则，对查询语句进行分析，选择最佳的执行路径，并生成相应的执行计划。下面将详细介绍OceanBase查询优化器的工作原理及其相关的优化算法。转存失败重新上传取消1）查询优化器的工作原理查询优化器的主要工作就是从多个可能的执行计划中选择一个最优的执行计划。它通过以下几个步骤完成这个过程：解析SQL。
OceanBase实验6：查看OceanBase执行计划
hyu1989的专栏
11-01 1513
实验6：查看OceanBase执行计划。
【OceanBase】27.OB的执行计划
weixin_43346403的博客
02-22 662
3.执行计划展示(EXPLAIN)-计划形状与算子信息。4.执行计划展示(EXPLAIN)-计划形状与算子信息。5.执行计划展示(EXPLAIN)-操作算子详细输出。6.执行计划展示(EXPLAIN)-示例。8.EXPLAIN与实时执行计划的对比。2.执行计划展示(EXPLAIN)9.查看执行计划的几种其它方式。7.实时执行计划展示。
OBCP第三章 SQL引擎高级技术-执行计划
明确的爱，真诚的喜欢，直接的厌恶，站在太阳底下的坦荡，被坚定的选择。
03-27 398
SQL 是一种“描述型”语言。与“过程型”语言不同，用户在使用 SQL 时，只描述了“要做什么”，而不是“怎么做”
第四章 oceanbase学习之查看oceanbase执行计划
RookieDBA的博客
04-27 1580
oceanbase执行计划
OceanBase实践练习二
03-15
OceanBase 实践练习二 OceanBase 是一个开源的分布式关系型数据库管理系统，提供了高性能、可扩展性强的数据存储解决方案。以下是 OceanBase 实践练习二的详细知识点总结： 1. OceanBase 部署环境数据清理 在部署...
OceanBase实践练习四
03-15
OceanBase实践练习四
淘宝Oceanbase云存储系统实践
02-20
国外的互联网巨头Amazon、Google、Microsoft、Yahoo都有各自的云存储系统，国内的淘宝也研发了自己的云存储系统Oceanbase，并开始应用到联机事务处理OLTP（On-lineTransactionProcessing）和联机分析处理OLAP（On-...
实践练习6：查看 OceanBase 执行计划
qinwen740的博客
03-30 2087
环境准备 机器信息 机器类型 虚拟机 IP 10.201.0.170, 10.201.0.171, 10.201.0.172, 10.201.0.173 网卡名 eth0 OS CentOS Linux release 7.9.2009 CPU 4C 内存 总内存 16G，可用内存 15G 磁盘1 磁盘 /dev/vda 200G 磁盘2 磁盘 /dev/vdb 300G 机器划分 角色 机器 备注 性能测
实践练习六：查看 OceanBase 执行计划
m0_55146438的博客
03-08 780
第一次执行压测shell脚本时，会报错，提示找不到funcs.sh，但funcs.sh在 安装dir/run/下的确是有这个文件，编辑runBenchmark.sh，将funcs.sh的路径改为绝对路径。编辑好配置文件后，需要在ob的目标库中建表。实验目标：使用benchmark导入数据并进行压测，查看top3sql的执行计划。修改完成后，如果执行还有报错，则根据实际错误提示进行对sql脚本进行修改即可。通过explain [extended] 查看top3 sql的逻辑执行计划。
查看OceanBase 执行计划
xxwana的博客
02-22 1597
1.学习如何查看实际执行计划2.学习理解执行计划中关键字的含义,以及为什么走这样的计划.3.实验的难点是执行sysbench 测试。后面的查看执行计划，可以按照参考文档对照执行。
oceanbase执行计划方法
11-16
根据提供的引用内容，oceanbase执行计划的方法可以在第四章中找到。具体方法如下： 1. 打开oceanbase客户端，连接到相应的数据库。 2. 在客户端中输入要执行的SQL语句，例如： ```sql explain select * from ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值