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

When used in the context of databases, memory refers to RAM directly addressable by the CPU as opposed to going through the I/O subsystem.

1
vote
This is a somewhat complicated question. When mysqld first starts up, it will allocate a bunch of memory for itself, but the operating system will actually delay allocation until the memory is first …
answered Apr 22 '14 by Morgan Tocker
13
votes
There are plenty of cases not to use the memory storage engine - and when InnoDB will be faster. You just need to think about concurrency and not trivial single threaded tests. If you have a large … enough buffer pool, then InnoDB will become entirely memory resident for read operations as well. Databases have caches. They warm themselves up! Also - do not underestimate the value of row-level …
answered Mar 21 '11 by Morgan Tocker
3
votes
MySQL cluster is built around an index structure that is optimized for memory fit; a T-tree. This is different from your regular storage engines in MySQL which use a B-tree or B+tree structure … , which can survive quite well out of memory fit assuming that you have some hot-spots / non uniform access (this is normally a safe assumption). If you want to build some sort of proof-of-concept, there's …
answered Jan 10 '12 by Morgan Tocker
1
vote
As others have answered your first question, I will answer the second: Do we need to make any changes in the my.ini file if any variable(s) are configured wrongly and also to improve the performan …
answered Dec 23 '15 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 to be InnoDB consuming the memory (assuming you collected this from when the problem was occurring): Total memory allocated 26217103360; in additional pool allocated 0 Dictionary memory allocated …
answered Aug 28 '14 by Morgan Tocker