Optimization paramters read-only mysql 5.7 database?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
0
down vote
favorite
What's the best way to configure a MySQL database that is only read-only, and will never have any modifications made to it?
1) I have increased my innodb_buffer_pool_size to 70% of available RAM
2) Increase query cache size to 40mb
Running against a load generator, after some time the database starts bottlenecking to only 1000 statements per second.
The configuration is 2-cores, 8GB ram 50GB SSD. The database contains a single InnoDB 13 GB table with the same exact query running on two indexed columns.
We are using a vertx server to hit the database. The symptom we see is that the web service performance degrades after 15-20 minutes of heavy load.
Where can the bottleneck be? What parameters should we optimize?
mysql
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
asked Nov 11 at 8:41
Joey Pinto
1013
add a comment |
up vote
0
down vote
favorite
What's the best way to configure a MySQL database that is only read-only, and will never have any modifications made to it?
1) I have increased my innodb_buffer_pool_size to 70% of available RAM
2) Increase query cache size to 40mb
Running against a load generator, after some time the database starts bottlenecking to only 1000 statements per second.
The configuration is 2-cores, 8GB ram 50GB SSD. The database contains a single InnoDB 13 GB table with the same exact query running on two indexed columns.
We are using a vertx server to hit the database. The symptom we see is that the web service performance degrades after 15-20 minutes of heavy load.
Where can the bottleneck be? What parameters should we optimize?
mysql
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
asked Nov 11 at 8:41
Joey Pinto
1013
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
What's the best way to configure a MySQL database that is only read-only, and will never have any modifications made to it?
1) I have increased my innodb_buffer_pool_size to 70% of available RAM
2) Increase query cache size to 40mb
Running against a load generator, after some time the database starts bottlenecking to only 1000 statements per second.
The configuration is 2-cores, 8GB ram 50GB SSD. The database contains a single InnoDB 13 GB table with the same exact query running on two indexed columns.
We are using a vertx server to hit the database. The symptom we see is that the web service performance degrades after 15-20 minutes of heavy load.
Where can the bottleneck be? What parameters should we optimize?
mysql
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
asked Nov 11 at 8:41
Joey Pinto
1013
What's the best way to configure a MySQL database that is only read-only, and will never have any modifications made to it?
1) I have increased my innodb_buffer_pool_size to 70% of available RAM
2) Increase query cache size to 40mb
Running against a load generator, after some time the database starts bottlenecking to only 1000 statements per second.
The configuration is 2-cores, 8GB ram 50GB SSD. The database contains a single InnoDB 13 GB table with the same exact query running on two indexed columns.
We are using a vertx server to hit the database. The symptom we see is that the web service performance degrades after 15-20 minutes of heavy load.
Where can the bottleneck be? What parameters should we optimize?
mysql
mysql
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
asked Nov 11 at 8:41
Joey Pinto
1013
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
asked Nov 11 at 8:41
Joey Pinto
1013
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
edited Nov 13 at 17:46
Max Vernon
49.6k13110216
49.6k13110216
asked Nov 11 at 8:41
Joey Pinto
1013
asked Nov 11 at 8:41
Joey Pinto
1013
asked Nov 11 at 8:41
Joey Pinto
1013
1013
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
I can think of several things that might help. But I can't be specific without seeing that query, plus SHOW CREATE TABLE.
If we can shrink the table/index size, there might be less I/O. If the index involves a UUID, then I will have lots to say.
Sometimes rearranging the index(es) helps.
If you are not using InnoDB, we need to discuss that.
Let's see SHOW GLOBAL STATUS; and SHOW VARIABLES; -- there are some metrics that will say how well the Query cache is doing, info about connections, whether the buffer_pool is adequately big, plus other things that might give clues.
In general, "you can't tune your way out of a performance problem."
For "readonly", add this to the config file:
read_only = ON
but I doubt if it will impact the performance.
answered Nov 11 at 17:04
Rick James
39.8k22257
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I can think of several things that might help. But I can't be specific without seeing that query, plus SHOW CREATE TABLE.
If we can shrink the table/index size, there might be less I/O. If the index involves a UUID, then I will have lots to say.
Sometimes rearranging the index(es) helps.
If you are not using InnoDB, we need to discuss that.
Let's see SHOW GLOBAL STATUS; and SHOW VARIABLES; -- there are some metrics that will say how well the Query cache is doing, info about connections, whether the buffer_pool is adequately big, plus other things that might give clues.
In general, "you can't tune your way out of a performance problem."
For "readonly", add this to the config file:
read_only = ON
but I doubt if it will impact the performance.
answered Nov 11 at 17:04
Rick James
39.8k22257
add a comment |
up vote
1
down vote
I can think of several things that might help. But I can't be specific without seeing that query, plus SHOW CREATE TABLE.
If we can shrink the table/index size, there might be less I/O. If the index involves a UUID, then I will have lots to say.
Sometimes rearranging the index(es) helps.
If you are not using InnoDB, we need to discuss that.
Let's see SHOW GLOBAL STATUS; and SHOW VARIABLES; -- there are some metrics that will say how well the Query cache is doing, info about connections, whether the buffer_pool is adequately big, plus other things that might give clues.
In general, "you can't tune your way out of a performance problem."
For "readonly", add this to the config file:
read_only = ON
but I doubt if it will impact the performance.
answered Nov 11 at 17:04
Rick James
39.8k22257
add a comment |
up vote
1
down vote
up vote
1
down vote
I can think of several things that might help. But I can't be specific without seeing that query, plus SHOW CREATE TABLE.
If we can shrink the table/index size, there might be less I/O. If the index involves a UUID, then I will have lots to say.
Sometimes rearranging the index(es) helps.
If you are not using InnoDB, we need to discuss that.
Let's see SHOW GLOBAL STATUS; and SHOW VARIABLES; -- there are some metrics that will say how well the Query cache is doing, info about connections, whether the buffer_pool is adequately big, plus other things that might give clues.
In general, "you can't tune your way out of a performance problem."
For "readonly", add this to the config file:
read_only = ON
but I doubt if it will impact the performance.
answered Nov 11 at 17:04
Rick James
39.8k22257
I can think of several things that might help. But I can't be specific without seeing that query, plus SHOW CREATE TABLE.
If we can shrink the table/index size, there might be less I/O. If the index involves a UUID, then I will have lots to say.
Sometimes rearranging the index(es) helps.
If you are not using InnoDB, we need to discuss that.
Let's see SHOW GLOBAL STATUS; and SHOW VARIABLES; -- there are some metrics that will say how well the Query cache is doing, info about connections, whether the buffer_pool is adequately big, plus other things that might give clues.
In general, "you can't tune your way out of a performance problem."
For "readonly", add this to the config file:
read_only = ON
but I doubt if it will impact the performance.
answered Nov 11 at 17:04
Rick James
39.8k22257
edited Nov 14 at 3:05
answered Nov 11 at 17:04
Rick James
39.8k22257
answered Nov 11 at 17:04
Rick James
39.8k22257
answered Nov 11 at 17:04
Rick James
39.8k22257
39.8k22257
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f222274%2foptimization-paramters-read-only-mysql-5-7-database%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
