network profile
| bio | website | |
|---|---|---|
| location | Cluj-Napoca, Romania | |
| age | ||
| visits | member for | 1 year, 1 month |
| seen | May 21 at 5:39 | |
| stats | profile views | 7 |
Just an enthusiast student...
|
Feb 20 |
comment |
Mysql: disable unused schemas Actually, if you have many databases, starting MySQL will not automatically put them in RAM... unless you explicitly set something like that up... which clearly you didn't... Have a look at MySQL configuration, maybe the cache sizes for InnoDB are too high or... something similar |
|
Jul 25 |
comment |
Why is DELETE so much slower than SELECT, then DELETE by id? @itsadok I wrote it as an answer :) . |
|
Jul 25 |
comment |
Why is DELETE so much slower than SELECT, then DELETE by id? @pconcepcion if you write EXPLAIN DELETE FROM...., it won't work. From what I know, it works only on SELECTs. |
|
Jul 25 |
comment |
Why is DELETE so much slower than SELECT, then DELETE by id? Yeah but.... you were right in the first place. If the field email is unindexed, then both DELETE and SELECT should work equally slow. Or: You say that the table is queried heavily. Maybe when you tried your first DELETE there was someone else running a really long transaction on those rows... |
|
Jul 25 |
comment |
Why is DELETE so much slower than SELECT, then DELETE by id? I guess you absolutely must post a SHOW CREATE TABLE and probably an EXPLAIN... too. |
|
May 16 |
comment |
Why doesn't InnoDB store the row count? Sounds very good (+1), you certainly made me curious about that option. If I ever get my hands on a table large enough to test this (let's say > 100K rows), I will definitely try it. |
|
May 16 |
comment |
Why doesn't InnoDB store the row count? @Remus I totall forgot about the SHOW TABLE STATUS. There is actually a row count there, I wonder how it's maintained (will look it up). I gave you a +1 , but I'll wait for other answers before accepting. Thank you. |
|
May 16 |
comment |
Why doesn't InnoDB store the row count? Such informations are quite useful. Think about a website that has to display to its admins the number of users registered, the number of users banned, the number of posts/topics (if it contains a forum) etc. Doing COUNT(*) makes sense in this case. True, you can store in a table named "statistics" or something similar, but wouldn't it be easier to avoid something like that ? |
|
May 16 |
comment |
Why doesn't InnoDB store the row count? @ypercube I know I saw a few times in phpmyadmin some row count values that were very off. Plus, there is a comment there saying something like "may not be accurate". |
|
May 16 |
comment |
Why doesn't InnoDB store the row count? Ok, so it's dependent on the isolation level, that makes sense. But it still can be implemented. |
