Melhorn: Scott0_: You don’t have to ask to ask, or state: “I have a question”, Don’t ask: “Is anyone around?” or “Can anyone help?”. Just Ask The Question. Also, please read: http://workaround.org/getting-help-on-irc

Abuaita: Wanted to make sure you were still active

Deraveniere: Brittman: http://pastie.org/pastes/10436537/text?key=aeswx6ysarhf0gbc1x2a

Brittman: Scott0_: i’m not, don’t ask me directly

Melo: You asked for the explains, so of course I would address you directly

Skirvin: Unless im missing something here

Ells: 5.5 finishes the explain faster

Daehn: On 5.5 its showing up as a slow query, on 5.1 it did not

Maietta: Scott0_: he was saying he’s not really around I think

Hans: If you want a dedicated slave get a consultant

Fazzinga: What’s with the aggressive reponse

Walp: I’ve waited paitiently all day, so no one can claim I asked for a ‘slave’

Losh: Do you have iostat output on old and new?

Celestine: Weird, old server does not have it installed or as a package

Nifong: Ok was hidden inside another package

Skeesick: Losh: http://pastie.org/private/rpe099pjlrihegpj68cx7g

Vallimont: This would indicate better performance on the new server

Bloodough: Could the binlof be slowing things down?

Losh: You need iostat -kx 1; over time on both

Ballar: Not sure I understand what you mean by over time

Foddrill: The command seems to print the output over and over again in kb

Prok: Do you mean run this during the query?

Brittman: Scott0_: also compare the handler stats: brand new connection with mysql client: select sql_no_cache .; show session status like ‘handler%’;

Brittman: Really gotta run now, good luck.

Stickler: This feels like finding a needle in a haystack

Menninger: Runngin both with sql_no_cache will still use the index won’t it?

Roese: Odd, a small amount of reading happens, and then it sits using memory for 30 seconds before printing the query results

Stjulian: Could it be because on the VPS upgrade I lost 2 CPUs?

Kmatz: Everything seems to be the same speed

Ebersole: Maybe im chasing something that doesn’t exist

Orantes: Based on perception instead of measurements

Jondle: What happens when you run repair table on an innodb table?

Evitt: I know it only applies to myisam and archive, but what happens if you DO run it on innodb?

Brockwell: Will it still set the tables to read only while it checks for example? or will it just error out and exit?

Panke: Gump: if I recall, nothing happens

Hemker: Gump: innodb has other procedures for repair and recovery

Sampogna: Gump: see innochecksum and http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

Carridine: Scott0_, i know. what i’m trying to do is add an automatic repair on startup for myisam databases

Fie: Gump: Try it and see, its quicker to type it on your system and try it than wait for one of us to tell you its ok

Correl: Gump: REPAIR TABLE any_innodb_table; and you will see

Semmes: Yeah yeah. that would take *effort*. i know, i’m a lazy piece of **** lol

Correl: Gump: You typed much longer to ask your question

Correl: Gump: SELECT LENGTH’REPAIR TABLE any_innodb_table;’; – 30 chars

Correl: Gump: SELECT LENGTH’what happens when you run repair table on an innodb table? i know it only applies to myisam and archive, but what happens if you DO run it on innodb? will it still set the tables to read only while it checks for example? or will it just error out and exit?’; – 256

Kravec: All my production tables are myisam at the moment. my long term plan is to migrate 1000+ LAMP stacks to innodb but i don’t actually have an innodb database to test on currently. but i guess i shouldn’t expect other people to do my testing for me