>The “output” from the sortmerge is fed into code that builds the BTree for
the table. This building of the BTree is sequential – fill the first
block, move on to the next block, and never have to go back.
James...
Thanks for your answer, so clearly.
Firstly:
I thought that the "block spli
Disagree all the way, numbers are numbers, and better than words, always.
Claudio
On May 9, 2012 7:22 PM, "Rick James" wrote:
> Numbers can be misleading �C one benchmark will show no difference; another
> will show 10x difference.
>
> Recommend you benchmark _*your*_ case.
>
> ** **
>
>
This thread is going on and on and on and on,
does anyone have time to actually measure I/O?
Let's make numbers talk.
Claudio
2012/5/9 Rick James
> A BTree that is small enough to be cached in RAM can be quickly
> maintained. Even the “block splits” are not too costly without the I/O.
>
> A b
A BTree that is small enough to be cached in RAM can be quickly maintained.
Even the “block splits” are not too costly without the I/O.
A big file that needs sorting – bigger than can be cached in RAM – is more
efficiently done with a dedicated “sort merge” program. A “big” INDEX on a
table m
On 5/9/2012 6:17 AM, Johan De Meersman wrote:
- Original Message -
From: "Claudio Nanni"
Yes indeed,
but I think we are talking about MySQL level deadlocks,
that can happen only with row level locking and transactions.
If the deadlock is generated at application level then you can ha
- Original Message -
> From: "Claudio Nanni"
> Yes indeed,
> but I think we are talking about MySQL level deadlocks,
> that can happen only with row level locking and transactions.
> If the deadlock is generated at application level then you can have
> it on anything, also blackhole :-)
Yes indeed,
but I think we are talking about MySQL level deadlocks,
that can happen only with row level locking and transactions.
If the deadlock is generated at application level then you can have it on
anything, also blackhole :-)
Claudio
2012/5/9 Johan De Meersman
> - Original Message --
- Original Message -
> From: "nixofortune"
>
> Few more things. You can't have a deadlock on Mylsam table. You can
You *can* have deadlocks in MyISAM; the concept is not related to any specific
engine - or even databases.
What you can't have, is deadlock on a single table :-)
--
Bier
