Here are the timings:
64-bit 5.0 Single Thread 1:00:12.17 total (~76% slower)
64-bit 4.1 Single Thread 41:38.07 total (~20% slower)
64-bit 4.0 Single Thread 34:50.23 total
I have been trying to get a stable configuration for a 64-bit mysql on
ubuntu for the past 6-8 months, and have
On Thu, 2005-06-16 at 21:06, Richard Dale wrote:
So we have recently started stress testing Mysql on an Opteron dual
CPU
machine running Ubuntu Hoary. We are using the 64-bit GCC
4.0.24-standard binary from mysql. The stress test that I'm currently
running on it involves inserting a
On Thu, 2005-06-16 at 21:06, Richard Dale wrote:
So we have recently started stress testing Mysql on an Opteron dual
CPU
machine running Ubuntu Hoary. We are using the 64-bit GCC
4.0.24-standard binary from mysql. The stress test that I'm currently
running on it involves inserting a
So we have recently started stress testing Mysql on an Opteron dual CPU
machine running Ubuntu Hoary. We are using the 64-bit GCC
4.0.24-standard binary from mysql. The stress test that I'm currently
running on it involves inserting a large database (from a mysqldump)
from three
We have been very successfully running MySQL in a production
environment one way or another for the past 6 years. We have recently
run into what I believe is a thread race condition while writing then
reading from a MyISAM table. The server we are experiencing this
problem on is a very
Hi,
We have recently upgraded to MySQL 4.0 (binary) from 3.23.50, and we
are seeing *all* MySQL queries freeze up every morning for about 25
seconds. I don't believe this is the standard run-of-the-mill MyISAM
locking problem people tend to run into, as queries in separate
databases
Any thoughts? What kind of internal locks might be generated? Is there
another command I can run to get the status of those queries that are
hanging? It shows 'None' for the state (NULL), I've never seen a
Aha.. So I had a brainstorm while driving to lunch. Is it possible
this is
We just upgraded to MySQL 4.0.20 (binary), and we use replication to a
slave running the same. We're having some difficulty deleting the relay
log files the slave creates. I'm fairly confused, as the manual clearly
says we shouldn't be having this problem:
According to the MySQL manual:
Relay
A week ago I posted that we were having horrible problems with MySQL's
replication failing and reconnecting (after years of reliable
operation). I still haven't come up with a solution to the problems, it
just looks like the master keeps tearing down the replication
connection, and the slave
We have suddenly run into a replication problem between our master and
our slave databases. It had been running without a problem for atleast
several months since our last upgrade, and for several years before
that. I've tried a number of debugging techniques, and now I'm hoping
somebody
somebody here can make sense of it. On the slave I get error messages
like:
040630 2:43:52 Slave: reconnected to master
'[EMAIL PROTECTED]:3306',replication resumed in log 'mysql-bin.163' at
position 37919441
It does that several times between 2:20am and 4:30am. and every few
Ah..
We've just switched from compiling our own MySQL to using your binary
distribution. This is the first time we've run MySQL in production from
one of your binary builds. We had to switch to a binary distribution
because we were running into the 1000 threads issue with the GLIBC
library
I'm having some problems with tables using autoincrementing primary
keys when I use InnoDB.. I've searched through the documentation at
Mysql and innobase's website, and havn't been able to find anything
saying this is a limitation of innodb, so I will assume this is a bug
(or
Im currently working on system for Managing http Session and would like
to use a heap table for storing the session information. Session
information is only of temporary intrest. But still I need an unique
ID for reference with some other Tabels storing dtaa for the session.
All these tables
14 matches
Mail list logo
