New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Here, let me Google that for you: http://bfy.tw/5Uvf
Cheers!
OOh they did not give the tune button ??
i read all over google, but that just not helped, anyone have experience with highly write/read mysql usage tune?
It's probably not mysql that's the issue, your code is likely shit.. No offense but yeh.... MySQL can be a bitch to work with under heavy applications. Try running the host as docker, openvz or something of that matter and run a cluster of MySQL server under a load balancer to help with the load.
https://github.com/major/MySQLTuner-perl
rm -rf *
shutdown now
what he said?
you only looking for exact answer :P try experiment before making any changes read MySQL documentation and watch your process closely.
Increase the # of maximum concurrent connections ?
Tweak the my.cnf file, it shouldn't be a problem.
Even if you have 128petabytes of ram...you still are going to ran into this issue....problem bad configurations....
Note:
Configurations of each linux module...is in accordance with resources and demand...
You my have huge resources but the config files are not allowing it to use all of it...
Just post my.cnf and other files...
+1
What are you running on it?
Don't forget to run from root directory so that it resolves the issue.
Try this google phrasse: MySQL: Too many connections my.cnf
And mentioned tool https://github.com/major/MySQLTuner-perl
might be also usefull
If you're fine with payed support - shoot me a personal message.
upgrade to mariadb
okay new error that occurs:
"mysqladmin -uroot -proot processlist"
i am gettin a lot of waiting table locks
| 676 | root | localhost | database | Query | 15 | Waiting for table level lock | SELECT * FROM pages ORDER BY page.id DESC LIMIT 0, 30
mysql> show engines;
| InnoDB | DEFAULT | Supports transactions, row-level locking, and foreign keys
9 rows in set (0.00 sec)
increase innodb caches, tune innodb writeback methods, put mysql temp dir on ramdisk etc.
but first of all: sort your code or app you are using/developing. as mentioned by others above, search for the root cause of your page receiving that much mysql requests...
seeing your other php-related thread I suggest to not put mysql-connections or request into loops with php and things alike...
also have a look into how persistent connections work and so on.