Skip to content
New issue

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

use_hugepage_resize_no_init warnings in db_bench #236

Open
dennhuan opened this issue Jun 10, 2022 · 2 comments
Open

use_hugepage_resize_no_init warnings in db_bench #236

dennhuan opened this issue Jun 10, 2022 · 2 comments

Comments

@dennhuan
Copy link

after build the software, did a db_bench run, it has a lot of WARNs:

WARN: void terark::use_hugepage_resize_no_init(terark::valvec*, size_t) [with T = unsigned char; size_t = long unsigned int]: madvise(MADV_HUGEPAGE, size=2551808[0x26F000]) = Invalid argument

my system is CentOS 7.7, with terarkdb dev1.4

@yapple
Copy link
Collaborator

yapple commented Jun 12, 2022

use_hugepage_resize_no_init just used in terark_zip table, do you want to use it ? or close it through cmake -DWITH_TERARK_ZIP=OFF

@Eshcar
Copy link

Eshcar commented Jun 19, 2022

Thank you for answering @yapple
before seeing your answer we switched to Ubuntu
However now after loading about 1.2 TB of data we get another error
/home/terarkdb/third-party/terark-zip/src/terark/util/mmap.cpp:146: void* terark::mmap_load(const char*, size_t*, bool, bool): errno=12 : mmap(fname=/media/terarkdb/DB_0//Terark-nnzO0j.zbs, READ SHARED, size=65589184) = Cannot allocate memory
which is also due to terark_zip
what is terark_zip used for?
what is the implication of closing this option on performance?
we are measuring performance of sequential load, overwrite, read-only, and mixed workload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants