hum, it's a innodb table? a myisam? what are you talking about high resource? locked tables? high write/read ?
2013/6/24 Marian Marinov <[email protected]> > Hi guys, > > I work with hosting companies and all of my clients have the same > irritating problem, one query taking a lot of time to finish and consuming > a lot of resources. > > So I have solved the same issue but with processes on the machine by > simply pausing(kill -STOP) these processes when the load is high and > continuing(kill -CONT) them when the server load goes down. > > I want to implement the same logic within MariaDB, so I can STOP/CONT the > thread that is executing this query. > > My idea is to implement this in the 'KILL query_id' function, so it will > accept one more argument, which will be either STOP or CONT. If the > parameter is not present, the default behavior should remain. > > What do you think about my approach? > > Marian > > ______________________________**_________________ > Mailing list: > https://launchpad.net/~maria-**developers<https://launchpad.net/~maria-developers> > Post to : > maria-developers@lists.**launchpad.net<[email protected]> > Unsubscribe : > https://launchpad.net/~maria-**developers<https://launchpad.net/~maria-developers> > More help : > https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp> > -- Roberto Spadim SPAEmpresarial
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
