查询语句压测时吞吐量太低

【详述】更新模型(Unique Key)
【背景】jmeter压测,数据量:1500w
【业务影响】
【StarRocks版本】例如:2.0.1 RELEASE
【集群规模】1fe+1be(fe与be混部)
【机器信息】CPU虚拟核/内存/网卡,:8C/16G/万兆
【附件】
压测查询语句:
select count(1) from ib_issue_unique_key_less where create_org_internal_code like ‘1.1.14.%’ and create_date>’${__RandomDate(yyyy-MM-dd,2018-01-01,2018-12-31,)} 00:00:00’ and create_date<’${__RandomDate(yyyy-MM-dd,2019-06-01,2020-06-01,)} 00:00:00’;

表结构:
CREATE TABLE ib_issue_unique_key_less (
id bigint(20) NOT NULL COMMENT “事件id”,
occur_org bigint(20) NULL COMMENT “事件发生网格id”,
create_org bigint(20) NOT NULL COMMENT “创建网格id”,
last_org bigint(20) NULL COMMENT “最后操作网格id”,
current_step_id bigint(20) NULL COMMENT “”,
source_kind bigint(20) NULL COMMENT “来源方式”,
important tinyint(4) NULL COMMENT “是否重大事件”,
urgent tinyint(4) NULL COMMENT “是否加急”,
is_emergency tinyint(4) NULL COMMENT “是否紧急事件”,
serial_number varchar(100) NULL COMMENT “事件的服务单号”,
subject varchar(450) NULL COMMENT “主题”,
occur_org_internal_code varchar(64) NULL COMMENT “发生网格内置编码”,
create_org_internal_code varchar(64) NOT NULL COMMENT “创建网格内置编码”,
last_org_internal_code varchar(64) NULL COMMENT “最后操作网格内置编码”,
last_user_name varchar(256) NULL COMMENT “最后操作用户名称”,
occur_location varchar(512) NULL COMMENT “发生地”,
complete_date datetime NULL COMMENT “办理结束时间”,
status varchar(60) NULL COMMENT “状态”,
create_user varchar(64) NULL COMMENT “”,
update_user varchar(64) NULL COMMENT “”,
occur_date datetime NULL COMMENT “发生时间”,
create_date datetime NOT NULL COMMENT “”,
update_date datetime NULL COMMENT “”,
remark varchar(4000) NULL COMMENT “备注”,
lat varchar(32) NULL COMMENT “纬度”,
lon varchar(32) NULL COMMENT “经度”,
coordinate_type varchar(32) NULL COMMENT “坐标类型”,
deal_time datetime NULL COMMENT “处理时间”,
target_org bigint(20) NULL COMMENT “当前处理部门”,
last_deal_date datetime NULL COMMENT “最后处理时间”,
supervise_level bigint(20) NULL COMMENT “督办层级”,
state_code bigint(20) NULL COMMENT “状态编码”,
complete_level bigint(20) NULL COMMENT “事件等级”,
issue_importance tinyint(4) NULL COMMENT “事件质量(0无效 1低 3中 6高)”,
is_deleted bigint(20) NULL DEFAULT “0” COMMENT “是否已删除”,
tenant_id varchar(12) NULL DEFAULT “000000” COMMENT “租户ID”,
category_code varchar(64) NULL COMMENT “分类code”,
has_attach_file tinyint(4) NULL COMMENT “有无附件”,
source_platform_code varchar(128) NULL COMMENT “来源平台编码”,
label_num smallint(6) NULL COMMENT “标签(1-6)”,
cgform_table_name varchar(128) NULL COMMENT “动态表名称”,
report_serial_number varchar(128) NULL COMMENT “上报方事件编号”,
instructed tinyint(4) NULL DEFAULT “0” COMMENT “领导批示 1有 0 没有”,
is_locked tinyint(4) NOT NULL DEFAULT “0” COMMENT “是否锁定”,
key_word_label varchar(128) NULL COMMENT “关键字标签”,
address_code varchar(512) NULL COMMENT “地址库Code”,
sync_sign tinyint(4) NULL COMMENT “同步件标识(1为同步件)”,
myself_completed tinyint(4) NULL COMMENT “是否自办结”,
trans_mode_in tinyint(4) NULL DEFAULT “0” COMMENT “流入类型”,
trans_mode_in_name varchar(256) NULL COMMENT “流入平台名称”,
trans_mode_out tinyint(4) NULL DEFAULT “0” COMMENT “流出类型”,
trans_mode_out_name varchar(256) NULL COMMENT “流出平台名称”,
supervisor_show_content varchar(64) NULL DEFAULT “正常” COMMENT “督办超时显示内容”,
handle_second bigint(20) NULL COMMENT “处理时长(秒)”,
version int(11) NULL COMMENT “数据标识”
) ENGINE=OLAP
UNIQUE KEY(id)
COMMENT “OLAP”
DISTRIBUTED BY HASH(id) BUCKETS 10
PROPERTIES (
“replication_num” = “1”,
“in_memory” = “false”,
“storage_format” = “DEFAULT”
);



配置太低了还是混部署,跑不起来,建议参考官网提供的配置进行测试