Re[2]: Some more about mysql perfomance.

Hi! > "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes: Peter> It's a pity what mysql misses something like PROFILE call for the Peter> query so I could check how much time is spent for different phases of Peter> query execution. MW> Any suggestions for the output for this? Peter> W

Re: Some more about mysql perfomance.

On Sun, Apr 08, 2001 at 12:46:43AM +0300, Michael Widenius wrote: > > Hi! > > > "Tim" == Tim Bunce <[EMAIL PROTECTED]> writes: > > Tim> On Sat, Apr 07, 2001 at 02:14:42AM +0300, Michael Widenius wrote: > >> > >> The reason singly queries are slower are of course that the > >> initializatio

Re[2]: Some more about mysql perfomance.

Hello Michael, Sunday, April 08, 2001, 4:21:18 AM, you wrote: Peter>> No it's not but it has just a couple of collisions per 100.000 Peter>> records. MW> The problem with a not unique key is that MySQL will do an extra check MW> if it should use the key during the optimization stage. If the

Re: Some more about mysql perfomance.

Hi! > "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes: Peter> Hello Michael, Peter> Saturday, April 07, 2001, 3:14:42 AM, you wrote: MW> Hi! >>> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes: Peter> Hello mysql, Peter> I made one more test of mysql perfomance. Peter> PII

Re: Some more about mysql perfomance.

Hi! > "Tim" == Tim Bunce <[EMAIL PROTECTED]> writes: Tim> On Sat, Apr 07, 2001 at 02:14:42AM +0300, Michael Widenius wrote: >> >> The reason singly queries are slower are of course that the >> initialization phase (reading the data from a socket, parsing, >> locking, checking which keys to

Re: Some more about mysql perfomance.

Hello Michael, Saturday, April 07, 2001, 3:14:42 AM, you wrote: MW> Hi! >> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes: Peter>> Hello mysql, Peter>> I made one more test of mysql perfomance. Peter>> PIII-700/768Mb/Linux 2.4.2 glbc 2.1.3 Peter>> I had the followings tab

Re[2]: Some more about mysql perfomance.

Hello Tim, Saturday, April 07, 2001, 3:21:52 AM, you wrote: >> The reason singly queries are slower are of course that the >> initialization phase (reading the data from a socket, parsing, >> locking, checking which keys to use) is about half of the query time. >> >> Peter> Heikki made tests

Re: Some more about mysql perfomance.

On Sat, Apr 07, 2001 at 02:14:42AM +0300, Michael Widenius wrote: > > The reason singly queries are slower are of course that the > initialization phase (reading the data from a socket, parsing, > locking, checking which keys to use) is about half of the query time. > > Peter> Heikki made test

Some more about mysql perfomance.

Hi! > "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes: Peter> Hello mysql, Peter> I made one more test of mysql perfomance. Peter> PIII-700/768Mb/Linux 2.4.2 glbc 2.1.3 Peter> I had the followings table with 12.000.000 rows (well I checked Peter> this with 1 rows as w

Some more about mysql perfomance.

Hello mysql, I made one more test of mysql perfomance. PIII-700/768Mb/Linux 2.4.2 glbc 2.1.3 I had the followings table with 12.000.000 rows (well I checked this with 1 rows as well but the speed does not differs much) in it and I checked how fast I can select data by hash ke