Heyas : does anyone knows.

 
Kuebler: Odd. would of though the limit would prevent it reading all rows.

Dolson: Could be fault of phpmyadmin

Rumery: Would ORDER BY fix it?

Weslow: For fun add ORDER BY emp_no ASC before LIMIT. :-

Eychaner: Might I add, selecting all is what’s slowing it down, if i just select emp_no it returns in milliseconds. Rumery, PMA forces ORDER BY, so it’s already there.

Peaslee: EXPLAIN is not good at showing limit optimization

Schimandle: Delzer: what else does it enforce?

Rumery: By the estimated rows it seems like the limit optimization might not be used. but as Boleware says.

Rimkus: I have a single uniquely-named table on multiple servers, and want to replicate them all to a single instance, is that possible?

Lelonek: Boleware, just that really.

Chimeno: Delzer: We don’t answer phpMyAdmin questions. See: #phpmyadmin

Reifman: Take out all the PMA I put in any of my messages.

Frankford: Did you run EXPLAIN SELECT * FROM salaries where emp_no 1000 LIMIT 11

Rumery: Delzer, because there seems to be a separate index for emp_no so it can be used for the simpler query

Peat: Rumery, yeah but I thought if I’m doing WHERE PK getting the other data wouldn’t be THAT much slower

Rumery: Delzer, yes, I agree with it being quite slow

Kimbrell: Boleware, http://pastebin.com/NqtHeuFw

Navaretta: Can you execute your query in mysql client?

Micallef: I just figured XAMPP has some CLI access, I’ll try executing my queries in there

Janczewski: Https://gist.github.com/9776c9010a82db7d0acf

Fournier: PMA is the culprit, sorry.

Gottshall: Change the emp_no that you are testing

Cordrey: Https://gist.github.com/8ef2fc07ad2976222a79

Klecker: Ok, so all queries are fast

Perea: If you run the same query multiple times, it could be cached by query cache

Onstead: Hi guys. I’m seeing some odd behaviour with MySQL. I have a single instance behind an AWS ElasticLoadBalancer trying to get a load test done. Basically when the test runs I can see 1000 connections back up on the ELB. So I thought MySQL couldn’t accept anymore connections because it was busy. However, CPU is at 15% and memory isn’t really being touched. ALso, when I run mysqladmin -p -i1 extended grep Threads_running the count just reports 1 which I’m guess

Dorchy: Ing is the thread query. Does anybody know if there’s anything else I can check? Running out of ideas

Mackall: Basically, the application servers are taking upto 8 seconds to connect to MySQL

Lafavor: Tricks: See http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_max_connections

Rumery: Tricks, does your setting limit it to 1000 ?

Jurgensen: Rumery, it’s already set to 4000 which is probably too high

Ryckman: I’m wondering if the box is dodgy

Squiers: Is there a way to see rows_examined for queries that do not make the slow_log?

Gidwani: Session status or the general log

Encino: I’m setting up multiple instances with multiple cnf files, but can’t seem to set the root p***word, i’m trying this: /usr/bin/mysqladmin –defaults-file=/db/pg.cnf -u root p***word ‘poodoo’

Biren: Gidwani: general log doesnt have rows_examined

Ullum: Gidwani: Is there a way to enable that?

Foss: But ghetting errors about not connecting to the default socket i’ve set the configs to listen on tcp

Gidwani: It isn’t super valuable because your’e going to run the query again to get explain plans right?

Gidwani: I mean it is nice to have but since the slow query log is based on time you can kind of work around it

Gidwani: Https://dev.mysql.com/doc/refman/5.5/en/execution-plan-information.html

Story: Heyas : does anyone knows where are the JSON UDFs for MySQL 5.6? I can’t find them in labs.mysql.com