Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 1268

MySQL version 5.5 - please also tag with mysql for search purposes.

0
votes
90% of memory available is too high for the buffer pool. The MySQL manual even says up to 80% + please allow for 10% additional overhead: The larger you set this value, the less disk I/O is needed t …
answered May 12 '14 by Morgan Tocker
18
votes
So I'm answering this question almost 4 years late: InnoDB file formats were conceived at a time when InnoDB was independent of the MySQL Server (for example: MySQL 5.1 could run two different versi …
answered Jan 11 '16 by Morgan Tocker
1
vote
You most likely have a .my.cnf file in your home directory, which is specifying a password. The clue here is that when you did not specify a password (sudo -u root), the error message is still saying …
answered Dec 21 '14 by Morgan Tocker
1
vote
Starting with MySQL 5.5 InnoDB uses a modified LRU algorithm to prevent table-scans from filling the buffer pool. By default only 3/8ths of the buffer pool is available to table-scans. In MySQL 5.6 …
answered Jun 18 '14 by Morgan Tocker
1
vote
Memory is not instrumented in MySQL until version 5.7 (currently in development), so this does make your question a bit of a guessing game. I can see from inside InnoDB status, that it doesn't appear …
answered Aug 28 '14 by Morgan Tocker