SSB基准测试-ClickHouse

最新推荐文章于 2024-06-26 11:03:25 发布
最新推荐文章于 2024-06-26 11:03:25 发布
阅读量480 收藏 4
点赞数 2
分类专栏： ssb基准测试 文章标签： clickhouse ssb基准测试
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/docsz/article/details/127665100
版权

1、SSB数据生成器

生成数据文件

git clone https://github.com/electrum/ssb-dbgen.git
cd ssb-dbgen
sed -i 's/^MACHINE.*=.*/MACHINE=LINUX/' makefile		# 将平台改为LINUX
make													# 生成可执行程序dbgen

# 利用dbgen生成示例数据，-T指定表，-s指定数据放大系数
./dbgen -s 50 -T c									# CUSTOMER表
	1500000 customer.tbl
./dbgen -s 20 -T p									# PART表
	1000000 part.tbl
./dbgen -s 50 -T s									# SUPPLIER表
	100000 supplier.tbl
./dbgen -s 1 -T d									# DATE_DIM表
	2556 date.tbl
./dbgen -s 50 -T l									# LINEORDER表
	300005811 lineorder.tbl

2、ClickHouse操作

2.1、创建数据库

CREATE DATABASE IF NOT EXISTS ssb;

2.2、 创建数据表

use ssb;

CREATE TABLE customer
(
        C_CUSTKEY       UInt32,
        C_NAME          String,
        C_ADDRESS       String,
        C_CITY          LowCardinality(String),
        C_NATION        LowCardinality(String),
        C_REGION        LowCardinality(String),
        C_PHONE         String,
        C_MKTSEGMENT    LowCardinality(String)
)
ENGINE = MergeTree ORDER BY (C_CUSTKEY);

CREATE TABLE lineorder
(
    LO_ORDERKEY             UInt32,
    LO_LINENUMBER           UInt8,
    LO_CUSTKEY              UInt32,
    LO_PARTKEY              UInt32,
    LO_SUPPKEY              UInt32,
    LO_ORDERDATE            Date,
    LO_ORDERPRIORITY        LowCardinality(String),
    LO_SHIPPRIORITY         UInt8,
    LO_QUANTITY             UInt8,
    LO_EXTENDEDPRICE        UInt32,
    LO_ORDTOTALPRICE        UInt32,
    LO_DISCOUNT             UInt8,
    LO_REVENUE              UInt32,
    LO_SUPPLYCOST           UInt32,
    LO_TAX                  UInt8,
    LO_COMMITDATE           Date,
    LO_SHIPMODE             LowCardinality(String)
)
ENGINE = MergeTree PARTITION BY toYear(LO_ORDERDATE) ORDER BY (LO_ORDERDATE, LO_ORDERKEY);

CREATE TABLE part
(
        P_PARTKEY       UInt32,
        P_NAME          String,
        P_MFGR          LowCardinality(String),
        P_CATEGORY      LowCardinality(String),
        P_BRAND         LowCardinality(String),
        P_COLOR         LowCardinality(String),
        P_TYPE          LowCardinality(String),
        P_SIZE          UInt8,
        P_CONTAINER     LowCardinality(String)
)
ENGINE = MergeTree ORDER BY P_PARTKEY;

CREATE TABLE supplier
(
        S_SUPPKEY       UInt32,
        S_NAME          String,
        S_ADDRESS       String,
        S_CITY          LowCardinality(String),
        S_NATION        LowCardinality(String),
        S_REGION        LowCardinality(String),
        S_PHONE         String
)
ENGINE = MergeTree ORDER BY S_SUPPKEY;

CREATE TABLE dates
(
    D_DATEKEY           UInt32,
    D_DATE              String,
    D_DAYOFWEEK         LowCardinality(String),
    D_MONTH             LowCardinality(String),
    D_YEAR              UInt32,
    D_YEARMONTHNUM      UInt32,
    D_YEARMONTH         String,
    D_DAYNUMINWEEK      UInt8,
    D_DAYNUMINMONTH     UInt8,
    D_DAYNUMINYEAR      UInt8,
    D_MONTHNUMINYEAR    UInt8,
    D_WEEKNUMINYEAR     UInt8,
    D_SELLINGSEASON     LowCardinality(String),
    D_LASTDAYINWEEKFL   LowCardinality(String),
    D_LASTDAYINMONTHFL  LowCardinality(String),
    D_HOLIDAYFL         LowCardinality(String),
    D_WEEKDAYFL         LowCardinality(String)
)
ENGINE = MergeTree ORDER BY D_DATEKEY;

SET max_memory_usage = 20000000000;

CREATE TABLE lineorder_flat
ENGINE = MergeTree ORDER BY (LO_ORDERDATE, LO_ORDERKEY)
AS SELECT
    l.LO_ORDERKEY AS LO_ORDERKEY,
    l.LO_LINENUMBER AS LO_LINENUMBER,
    l.LO_CUSTKEY AS LO_CUSTKEY,
    l.LO_PARTKEY AS LO_PARTKEY,
    l.LO_SUPPKEY AS LO_SUPPKEY,
    l.LO_ORDERDATE AS LO_ORDERDATE,
    l.LO_ORDERPRIORITY AS LO_ORDERPRIORITY,
    l.LO_SHIPPRIORITY AS LO_SHIPPRIORITY,
    l.LO_QUANTITY AS LO_QUANTITY,
    l.LO_EXTENDEDPRICE AS LO_EXTENDEDPRICE,
    l.LO_ORDTOTALPRICE AS LO_ORDTOTALPRICE,
    l.LO_DISCOUNT AS LO_DISCOUNT,
    l.LO_REVENUE AS LO_REVENUE,
    l.LO_SUPPLYCOST AS LO_SUPPLYCOST,
    l.LO_TAX AS LO_TAX,
    l.LO_COMMITDATE AS LO_COMMITDATE,
    l.LO_SHIPMODE AS LO_SHIPMODE,
    c.C_NAME AS C_NAME,
    c.C_ADDRESS AS C_ADDRESS,
    c.C_CITY AS C_CITY,
    c.C_NATION AS C_NATION,
    c.C_REGION AS C_REGION,
    c.C_PHONE AS C_PHONE,
    c.C_MKTSEGMENT AS C_MKTSEGMENT,
    s.S_NAME AS S_NAME,
    s.S_ADDRESS AS S_ADDRESS,
    s.S_CITY AS S_CITY,
    s.S_NATION AS S_NATION,
    s.S_REGION AS S_REGION,
    s.S_PHONE AS S_PHONE,
    p.P_NAME AS P_NAME,
    p.P_MFGR AS P_MFGR,
    p.P_CATEGORY AS P_CATEGORY,
    p.P_BRAND AS P_BRAND,
    p.P_COLOR AS P_COLOR,
    p.P_TYPE AS P_TYPE,
    p.P_SIZE AS P_SIZE,
    p.P_CONTAINER AS P_CONTAINER
FROM lineorder AS l
INNER JOIN customer AS c ON c.C_CUSTKEY = l.LO_CUSTKEY
INNER JOIN supplier AS s ON s.S_SUPPKEY = l.LO_SUPPKEY
INNER JOIN part AS p ON p.P_PARTKEY = l.LO_PARTKEY;

2.3、 导入数据

clickhouse-client -u default -h 192.168.200.215 --port 9090 --password ClickHouse*8 --query "INSERT INTO ssb.dates FORMAT CSV" < /data/ssb-dbgen/date.tbl

clickhouse-client -u default -h 192.168.200.215 --port 9090 --password ClickHouse*8 --query "INSERT INTO ssb.customer FORMAT CSV" < /data/ssb-dbgen/customer.tbl

clickhouse-client -u default -h 192.168.200.215 --port 9090 --password ClickHouse*8 --query "INSERT INTO ssb.part FORMAT CSV" < /data/ssb-dbgen/part.tbl

clickhouse-client -u default -h 192.168.200.215 --port 9090 --password ClickHouse*8 --query "INSERT INTO ssb.supplier FORMAT CSV" < /data/ssb-dbgen/supplier.tbl

clickhouse-client -u default -h 192.168.200.215 --port 9090 --password ClickHouse*8 --query "INSERT INTO ssb.lineorder FORMAT CSV" < /data/ssb-dbgen/lineorder.tbl

3、执行标准SQL-单表查询

3.1、执行SQL

--Q1.1
SELECT SUM(LO_REVENUE) AS REVENUE
FROM lineorder join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
WHERE D_YEAR = 1993 AND LO_DISCOUNT BETWEEN 1 AND 3 AND LO_QUANTITY < 25;


--Q1.2
SELECT SUM(LO_REVENUE) AS REVENUE
FROM lineorder
join dates ON toDate32(LO_ORDERDATE) = toDate32(D_DATEKEY)
WHERE D_YEARMONTHNUM = 199401
AND LO_DISCOUNT BETWEEN 4 AND 6
AND LO_QUANTITY BETWEEN 26 AND 35;


--Q1.3
SELECT SUM(LO_REVENUE) AS REVENUE
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
WHERE D_WEEKNUMINYEAR = 6 AND D_YEAR = 1994
AND LO_DISCOUNT BETWEEN 5 AND 7
AND LO_QUANTITY BETWEEN 26 AND 35;


--Q2.1
SELECT SUM(LO_REVENUE) AS LO_REVENUE, D_YEAR, P_BRAND
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
JOIN part ON LO_PARTKEY = P_PARTKEY
JOIN supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE P_CATEGORY = 'MFGR#12' AND S_REGION = 'AMERICA'
GROUP BY D_YEAR, P_BRAND
ORDER BY D_YEAR, P_BRAND;


--Q2.2
SELECT SUM(LO_REVENUE) AS LO_REVENUE, D_YEAR, P_BRAND
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join part on LO_PARTKEY = P_PARTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE P_BRAND BETWEEN 'MFGR#2221' AND 'MFGR#2228' AND S_REGION = 'ASIA'
GROUP BY D_YEAR, P_BRAND
ORDER BY D_YEAR, P_BRAND;


--Q2.3
SELECT SUM(LO_REVENUE) AS LO_REVENUE, D_YEAR, P_BRAND
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join part on LO_PARTKEY = P_PARTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE P_BRAND = 'MFGR#2239' AND S_REGION = 'EUROPE'
GROUP BY D_YEAR, P_BRAND
ORDER BY D_YEAR, P_BRAND;


--Q3.1
SELECT C_NATION, S_NATION, D_YEAR, SUM(LO_REVENUE) AS LO_REVENUE
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE C_REGION = 'ASIA' AND S_REGION = 'ASIA'AND D_YEAR >= 1992 AND D_YEAR <= 1997
GROUP BY C_NATION, S_NATION, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;


--Q3.2
SELECT C_CITY, S_CITY, D_YEAR, SUM(LO_REVENUE) AS LO_REVENUE
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE C_NATION = 'UNITED STATES' AND S_NATION = 'UNITED STATES'
AND D_YEAR >= 1992 AND D_YEAR <= 1997
GROUP BY C_CITY, S_CITY, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;


--Q3.3
SELECT C_CITY, S_CITY, D_YEAR, SUM(LO_REVENUE) AS LO_REVENUE
FROM lineorder
join dates on  toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE (C_CITY='UNITED KI1' OR C_CITY='UNITED KI5')
AND (S_CITY='UNITED KI1' OR S_CITY='UNITED KI5')
AND D_YEAR >= 1992 AND D_YEAR <= 1997
GROUP BY C_CITY, S_CITY, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;


--Q3.4
SELECT C_CITY, S_CITY, D_YEAR, SUM(LO_REVENUE) AS LO_REVENUE
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE (C_CITY='UNITED KI1' OR C_CITY='UNITED KI5') AND (S_CITY='UNITED KI1' OR S_CITY='UNITED KI5') AND D_YEARMONTH = 'DEC1997'
GROUP BY C_CITY, S_CITY, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;


--Q4.1
SELECT D_YEAR, C_NATION, SUM(LO_REVENUE) - SUM(LO_SUPPLYCOST) AS PROFIT
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
join part on LO_PARTKEY = P_PARTKEY
WHERE C_REGION = 'AMERICA' AND S_REGION = 'AMERICA' AND (P_MFGR = 'MFGR#1' OR P_MFGR = 'MFGR#2')
GROUP BY D_YEAR, C_NATION
ORDER BY D_YEAR, C_NATION;


--Q4.2
SELECT D_YEAR, S_NATION, P_CATEGORY, SUM(LO_REVENUE) - SUM(LO_SUPPLYCOST) AS PROFIT
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
join part on LO_PARTKEY = P_PARTKEY
WHERE C_REGION = 'AMERICA'AND S_REGION = 'AMERICA'
AND (D_YEAR = 1997 OR D_YEAR = 1998)
AND (P_MFGR = 'MFGR#1' OR P_MFGR = 'MFGR#2')
GROUP BY D_YEAR, S_NATION, P_CATEGORY
ORDER BY D_YEAR, S_NATION, P_CATEGORY;


--Q4.3
SELECT D_YEAR, S_CITY, P_BRAND, SUM(LO_REVENUE) - SUM(LO_SUPPLYCOST) AS PROFIT
FROM lineorder
join dates ON toDate(LO_ORDERDATE) = toDate(D_DATEKEY)
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
join part on LO_PARTKEY = P_PARTKEY
WHERE C_REGION = 'AMERICA'AND S_NATION = 'UNITED STATES'
AND (D_YEAR = 1997 OR D_YEAR = 1998)
AND P_CATEGORY = 'MFGR#14'
GROUP BY D_YEAR, S_CITY, P_BRAND
ORDER BY D_YEAR, S_CITY, P_BRAND;

3.2、单表查询结果

在这里插入图片描述

4、执行标准SQL-多表查询

4.1、执行SQL

--Q1.1
select sum(LO_REVENUE) as revenue
from lineorder join dates ON toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
WHERE D_YEAR = 1993 AND LO_DISCOUNT BETWEEN 1 AND 3 AND LO_QUANTITY < 25;


--Q1.2
select sum(LO_REVENUE) as revenue
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
WHERE D_YEARMONTHNUM = 199401
AND LO_DISCOUNT BETWEEN 4 AND 6
AND LO_QUANTITY BETWEEN 26 AND 35;


--Q1.3
select sum(LO_REVENUE) as revenue
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
WHERE D_WEEKNUMINYEAR = 6 AND D_YEAR = 1994
AND LO_DISCOUNT BETWEEN 5 AND 7
AND LO_QUANTITY BETWEEN 26 AND 35;


--Q2.1
select sum(LO_REVENUE) as lo_revenue, D_YEAR, P_BRAND
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join part on LO_PARTKEY = P_PARTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
WHERE P_CATEGORY = 'MFGR#12' AND S_REGION = 'AMERICA'
GROUP BY D_YEAR, P_BRAND
ORDER BY D_YEAR, P_BRAND;


--Q2.2
select sum(LO_REVENUE) as lo_revenue, D_YEAR, P_BRAND
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join part on LO_PARTKEY = P_PARTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
WHERE P_BRAND BETWEEN 'MFGR#2221' AND 'MFGR#2228' AND S_REGION = 'ASIA'
GROUP BY D_YEAR, P_BRAND
ORDER BY D_YEAR, P_BRAND;


--Q2.3
select sum(LO_REVENUE) as lo_revenue, D_YEAR, P_BRAND
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join part on LO_PARTKEY = P_PARTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
WHERE P_BRAND = 'MFGR#2239' AND S_REGION = 'EUROPE'
GROUP BY D_YEAR, P_BRAND
ORDER BY D_YEAR, P_BRAND;


--Q3.1
select C_NATION, S_NATION, D_YEAR, sum(LO_REVENUE) as LO_REVENUE
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer on LO_CUSTKEY = C_CUSTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
WHERE C_REGION = 'ASIA' AND S_REGION = 'ASIA'AND D_YEAR >= 1992 AND D_YEAR <= 1997
GROUP BY C_NATION, S_NATION, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;


--Q3.2
select C_CITY, S_CITY, D_YEAR, sum(LO_REVENUE) AS LO_REVENUE
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer on LO_CUSTKEY = C_CUSTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
WHERE C_NATION = 'UNITED STATES' AND S_NATION = 'UNITED STATES'
AND D_YEAR >= 1992 AND D_YEAR <= 1997
GROUP BY C_CITY, S_CITY, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;

--Q3.3
select C_CITY, S_CITY, D_YEAR, SUM(LO_REVENUE) AS LO_REVENUE
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE (C_CITY='UNITED KI1' OR C_CITY='UNITED KI5')
AND (S_CITY='UNITED KI1' OR S_CITY='UNITED KI5')
AND D_YEAR >= 1992 AND D_YEAR <= 1997
GROUP BY C_CITY, S_CITY, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;

--Q3.4
select C_CITY, S_CITY, D_YEAR, SUM(LO_REVENUE) AS LO_REVENUE
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
WHERE (C_CITY='UNITED KI1' OR C_CITY='UNITED KI5') AND (S_CITY='UNITED KI1' OR S_CITY='UNITED KI5') AND D_YEARMONTH = 'DEC1997'
GROUP BY C_CITY, S_CITY, D_YEAR
ORDER BY D_YEAR ASC, LO_REVENUE DESC;


--Q4.1
select D_YEAR, C_NATION, SUM(LO_REVENUE) - SUM(LO_SUPPLYCOST) AS PROFIT
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer ON LO_CUSTKEY = C_CUSTKEY
join supplier ON LO_SUPPKEY = S_SUPPKEY
join part on LO_PARTKEY = P_PARTKEY
WHERE C_REGION = 'AMERICA' AND S_REGION = 'AMERICA' AND (P_MFGR = 'MFGR#1' OR P_MFGR = 'MFGR#2')
GROUP BY D_YEAR, C_NATION
ORDER BY D_YEAR, C_NATION;


--Q4.2
select D_YEAR, S_NATION, P_CATEGORY, SUM(LO_REVENUE) - SUM(LO_SUPPLYCOST) AS PROFIT
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer on LO_CUSTKEY = C_CUSTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
join part on LO_PARTKEY = P_PARTKEY
WHERE C_REGION = 'AMERICA'AND S_REGION = 'AMERICA'
AND (D_YEAR = 1997 OR D_YEAR = 1998)
AND (P_MFGR = 'MFGR#1' OR P_MFGR = 'MFGR#2')
GROUP BY D_YEAR, S_NATION, P_CATEGORY
ORDER BY D_YEAR, S_NATION, P_CATEGORY;

--Q4.3
select D_YEAR, S_CITY, P_BRAND, SUM(LO_REVENUE) - SUM(LO_SUPPLYCOST) AS PROFIT
from lineorder
join dates on toYYYYMMDD(LO_ORDERDATE) = D_DATEKEY
join customer on LO_CUSTKEY = C_CUSTKEY
join supplier on LO_SUPPKEY = S_SUPPKEY
join part on LO_PARTKEY = P_PARTKEY
WHERE C_REGION = 'AMERICA'AND S_NATION = 'UNITED STATES'
AND (D_YEAR = 1997 OR D_YEAR = 1998)
AND P_CATEGORY = 'MFGR#14'
GROUP BY D_YEAR, S_CITY, P_BRAND
ORDER BY D_YEAR, S_CITY, P_BRAND;

4.2、多表查询结果

在这里插入图片描述

docsz
关注
专栏目录
Clickhouse（20.4.2.9） SSB性能测试
聂雄超的博客
02-24 1687
SSB（Star Schema Benchmark）是麻省州立大学波士顿校区的研究人员定义的基于现实商业应用的数据模型，业界公认用来模拟决策支持类应用，比较公正和中立。
【JMeter-ClickHouse】使用JMeter对ClickHouse的查询性能进行压测
weixin_53543905的博客
03-10 1842
ClickHouse的连接驱动JMeter自身没有集成，需要我们自行添加，否则就会出现找不到驱动的异常。将star schema转换为flat schema，为后面查询性能压测做准备。这里选取几个常用的监听器进行举例，其中响应时间单位均为。路径下，如果有重复的就跳过添加。将所有jar包放入到。【JMeter-ClickHouse】使用JMeter对ClickHouse的查询性能进行压测
SSB基准测试-模型介绍
com728871的博客
07-04 1275
SSB（Star Schema Benchmark）是麻省州立大学波士顿校区的研究人员定义的基于现实商业应用的数据模型，业界公认用来模拟决策支持类应用，比较公正和中立。学术界和工业界普遍采用它来评价决策支持技术方面应用的性能。全...
clickhouse SSB 性能测试
司马懿的西山居
11-29 1901
SSB（Star Schema Benchmark）的介绍论文地址： https://www.cs.umb.edu/~poneil/StarSchemaB.PDF 官网链接 https://clickhouse.com/docs/en/getting-started/example-datasets/star-schema/ 如果安装系统时，时最小化mini安装，经常会提示很多命令不存在 提示 git 不存在，使用 yum install git 安装即可 提示 make: command not fo
clickhouse--基于 Yandex.Metrica 数据集进行基准测试
penriver的博客
01-11 820
如何基于 Yandex.Metrica 数据集，在服务器上运行基本的 ClickHouse 性能测试呢？ 本文提供在单机版上进行 ClickHouse 性能测试的指导，如果想在clickhouse集群上进行性能测试，只需要将表建成分布式表即可。
达梦列式存储和clickhouse基准测试
u011197085的博客
11-22 868
由于我无法直接访问数据库或执行基准测试，我无法提供实际的测试数据。但是，我可以帮助您制定测试计划和方法。如果您需要具体的SQL脚本或测试工具的建议，请告诉我。对于性能测试结果的呈现，可以使用电子表格软件如Microsoft Excel或Google Sheets来记录数据，并使用它们的图表功能来可视化结果。要验证达梦BigTable和ClickHouse的性能差异，您需要进行一系列基准测试。基准测试通常包括多个步骤，如准备测试环境、设计测试案例、执行测试、收集数据和分析结果。
ssb-invites-db:使用ssb-invites-schema进行盾牌邀请的flumeview-reduce
05-08
ssb-invites-db 一种针对scuttle- ssb插件使用scuttle- flumeview-reduce。 允许在root记录（例如的顶部使用多态邀请/回复系统。 // Plug into a Scuttlebot server Server.use(require('ssb-invites-db')) // ...
ssb-bot-feed：Scuttlebutt机器人，可读取RSS提要并自动发布更新
02-01
ssb-bot-feed Scuttlebutt机器人可以自动读取RSS提要并发布更新 用法 下载并运行 npm install -g ssb-bot-feed 句法： ssb-bot-feed [feed1] [feed2] [feedN] 例： ssb-bot-feed ...
ssb-room-client:与房间服务器交互的秘密堆栈插件
08-04
ssb-房间-客户端 接受与 SSB 房间服务器交互的插件。 这应该在远程调用服务器的应用程序上安装和使用，因此客户端。 请注意，某些房间可能具有附加功能，例如使用 SSB 和 HTTP 邀请登录，因此也可能值得安装和 。 ...
ClickHouse 性能测试
最新发布
ClickHouseDB的博客
06-26 908
例如，当我们发现一个竞争数据库引擎使用 sum 聚合函数完成查询的速度是我们的两倍时，我们测试了几十种 sum 的实现，最终找到了性能最佳的（参见关于此的演讲，俄语）。软件是一个不断变化的有机体，而 ClickHouse 的变化速度非常快——为了解释这一规模，仅在 2021 年 7 月，我们就合并了由 60 位不同作者提交的 319 个拉取请求（实时统计数据在这里）。这个测试有更多的失败模式，而不仅仅是功能测试，更糟糕的是，这些失败有些是定量的，而不是二元的。最近的一次是我们提到的 PR 带来的加速。
Clickhouse 官方测试数据集之SSB
vkingnew 的技术博客
06-17 3401
1.SSB概述 概述： 2.SSB操作步骤： 3.SSB测试脚本：
TPC-C 、TPC-H、TPC-DS和SSB测试基准（Benchmark）介绍
Laurence的技术博客
12-06 3420
TPC是一个非盈利组织，致力于定义事务处理和数据库benchmark，其提供了面向不同应用场景的多种Benchmark: https://www.tpc.org/information/benchmarks5.asp 下图是对几个主要的benchmark的汇总： 接下来，我们着重介绍一上最广泛讨论的四种Benchmark.面向OLTP测试，也就是测试关系型数据库的数据集。面向OLTP测试，也就是测试分析型数据库/数据仓库的数据集，业务场景是“商品零售业”。TPC-H是一款面向商品零售业的决策支持系统测试
第3.0章：StarRocks SSB性能测试（拓展篇）
流木的博客
01-07 4617
SSB（Star Schema Benchmark）是麻省州立大学波士顿校区的研究人员定义的基于现实商业应用的数据模型，是业界公认的可用来模拟决策支持类应用的测试集合，其测试结果比较公正和中立。学术界和工业界普遍采用它来评价决策支持技术类应用的性能，以此全方位评测系统的整体商业计算综合能力。 通过SSB测试集合，我们可以方便的对比各种OLAP产品的基础性能指标，StarRocks的SSB测试报告可以在官网获取，地址为： StarRocks - 新一代极速全场景MPP数据库https://www.star
SSB基准测试-Apache Doris
docsz的博客
10-28 712
apache doris性能测试
SSB数据集导入ClickHouse
鲸鱼
10-21 871
进入clickhouse-client时加一个-m的参数即可。 clickhouse-client -m -h 10.43.237.127 -u clickhouse_operator --password clickhouse_operator_password
clickhouse-压测
line_on_database的博客
08-24 1167
数据集可以使用，也可以用ssb-dbgen来准备。
以 100GB SSB 性能测试为例，通过 ByteHouse 云数仓开启你的数据分析之路
字节跳动技术团队官方博客
04-21 3750
动手点关注干货不迷路I. 传统数仓的演进：云数仓近年来，随着数据“爆炸式”的增长，越来越多的数据被产生、收集和存储。而挖掘海量数据中的真实价值，从其中提取商机并洞见未来，则成了现代企业和组织不可忽视的命题。随着数据量级和复杂度的增大，数据分析处理的技术架构也在不断演进。在面对海量数据分析时，传统 OLAP 技术架构中的痛点变得越来越明显，如扩容缩容耗时长，导致资源利用率偏低，成本居高不下；以及运维...
Doris【部署 02】Linux环境Doris数据库进行SSB基准测试
Java与大数据相关实践内容分享！
05-16 1368
Linux环境Doris数据库进行SSB基准测试
大数据应用之 --- clickhouse性能测试
qq_41187116的博客
07-10 1077
大数据应用之 --- clickhouse性能测试ssb及扩展测试，在ssb的基础行增加了5和6的测试。
Kramers-Kronig接收器在SSB-OFDM-RoF链路的应用与优化
在"应用克雷默-科尔尼接收器于SSB-OFDM-RoF链路中的研究"这篇论文中，作者杨成（蔡沅成）、凌云（*）、高翔、许渤和邱昆探讨了一种新的技术方案，即在基于光学远程混频的单边带正交频分复用无线光通信（SSB-OFDM-RoF...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值