We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
表结构,造100w行数据 CREATE TABLE sbtest1(idint(11) NOT NULL AUTO_INCREMENT,kint(11) NOT NULL DEFAULT '0',cvarchar(4096) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '',pad char(60) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '', PRIMARY KEY (id), KEY k_1 (k) ) ENGINE=XENGINE
CREATE TABLE
(
int(11) NOT NULL AUTO_INCREMENT,
int(11) NOT NULL DEFAULT '0',
varchar(4096) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '',
char(60) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '', PRIMARY KEY (
), KEY
) ) ENGINE=XENGINE
简单的查询
同样表结构和数据,换成innodb没有问题
The text was updated successfully, but these errors were encountered:
如果发现查询性能不符合预期,请检查下参数配置,是否L0/L1层存在层数堆积情况。当层数堆积较多时,lsm-tree的的range查询由于需要做多路归并,性能会受到影响
Sorry, something went wrong.
No branches or pull requests
表结构,造100w行数据
CREATE TABLE
sbtest1(
idint(11) NOT NULL AUTO_INCREMENT,
kint(11) NOT NULL DEFAULT '0',
cvarchar(4096) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '',
padchar(60) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '', PRIMARY KEY (
id), KEY
k_1(
k) ) ENGINE=XENGINE
简单的查询
![1685607317977](https://private-user-images.githubusercontent.com/135212723/242532042-9aadd08e-35c7-4481-9271-2ae05866225e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMwNzMxNTksIm5iZiI6MTcyMzA3Mjg1OSwicGF0aCI6Ii8xMzUyMTI3MjMvMjQyNTMyMDQyLTlhYWRkMDhlLTM1YzctNDQ4MS05MjcxLTJhZTA1ODY2MjI1ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwN1QyMzIwNTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04MWU4NDVjNGM2MmU2ODg4ZDk4YWEyNDhhMjkzY2RlMTFlNjZiMDk1MWMzZTcxNTNjMTgzMGQ2YmI4OWI2YTA4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.OtfAUNKGfoy-EFIRZeic8cFcb6snAsz9ZhKCJImeFoM)
同样表结构和数据,换成innodb没有问题
The text was updated successfully, but these errors were encountered: