-
Notifications
You must be signed in to change notification settings - Fork 6
Added Readme.md for -t all option #30
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
base: main
Are you sure you want to change the base?
Conversation
|
||
The suite is particularly useful for: | ||
|
||
- Initial database cluster setup verification |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe just "initial database setup verification", not necessary only cluster
- Infrastructure performance testing | ||
- Database configuration validation | ||
|
||
## Base Tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you are writing the README, it makes sense to describe the light/medium/heavy tables before you describe Insert/Update
Also the tenants table and the idea of the tenant-aware operations
- `--workers`: Controls the number of concurrent workers for parallel operations | ||
- `--chunk`: Controls the number of loops for insert and update operations | ||
|
||
## Reference Results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move the results to separate file not to polute README... because I'd expect a lot of combinations of results. Maybe it would make sense to have:
results/test.sh << here you just put all the command lines you executed
results/macbook-pro-m1.md << the results themesleves
results/macbook-pro-m4.md
Disk Performance | ||
|
||
``` bash | ||
> fio --name=randwrite --ioengine=sync --rw=randwrite --bs=4k --size=1G --numjobs=1 --runtime=60 --group_reporting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1G could be not enough, especially for servers, I'd use at least 8G not to get it cached by RAID caches
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have tested with 32G, it showed even more huge difference in performance between MacBook PRO and prod-like server
======================================================================================================================== | ||
|
||
database settings checks: | ||
- innodb_buffer_pool_size (aka primary DB cache)........................ 134217728 ERR: min value should be at least 8589934592 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ERR means your DB is misconfigured, it's better to have OK everywhere
Especially in case of PostgreSQL
======================================================================================================================== | ||
|
||
database settings checks: | ||
- shared_buffers (aka primary DB cache)................................. 128MB ERR: min value should be at least 1073741824 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same issue - there must be no ERR - the results could be impacted by these settings with ERR's
No description provided.