Thanks Mike. Seems like even with handler, the big query process is still consuming all my RAM and swap and being killed with error 'VM: killing process mysql __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)'
I would like to find a startup parameter either for client or server to limit per thread memory usage. -----Original Message----- From: mos [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 4:39 PM To: [EMAIL PROTECTED] Subject: Re: tuning suggestion for large query At 10:40 AM 9/1/2004, you wrote: >Hi, > >We have a job that do 'select * from big-table' on a staging mysql >database, then dump to data warehouse, it is scheduled to run once a day, >but may be run manually. Also we have several other small OLTP database on >the same server. >When the big job run, it would use all the physical mem and swap, all >other process slow down because of this. > >I would like to limit the resource usage for each mysql client so that >they can use only certain max amount of RAM, and don't select everything >into memory before display it to users. However, I couldn't find any >parameter would let me implement it. >Anybody ever encounter the same issue before? Please share your experience. > >Thanks. > >- Try the Handler command with an Index if you need the results sorted. It may do the trick. :) Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
