count(*) is slow in innodb due to Multi Versioning. Which table type are you
using ?
Thanx
Alex
On 6/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi everybody,
MySQL 5.0.21 running on RedHat EL4, 2GHz CPU, 2,5GB RAM, RAID5/128MB
RAM. At one point I had to issue the following query on a
Innodb tables do not cache the rowcount like MyISAM tables
do, so mysql has to walk the entire table to get a count. If you have
a unique index, it should be able to scan that instead, which will be
faster.
On Sat, 2006-06-17 at 20:32 +0530, Alex Arul wrote:
count(*) is slow in innodb due to
I just upgraded to mysql 5, and can't restart the daemon.
060617 11:57:22 [Warning] No argument was provided to --log-bin, and
--log-bin-index was not used; so replication may break when this MySQL
server acts as a master and has his hostname changed!! Please use
'--log-bin=spring-bin' to avoid
So, you're looking at 150-300 databases and ~31-62k tables based on your
numbers? MySQL should be able to handle that, as should your OS, but the
most important part IMO is how your clients will be using their
data(bases). What sort of queries, how many, etc. Will it be possible for
one client to
Anthony Ettinger wrote:
I just upgraded to mysql 5, and can't restart the daemon.
060617 11:57:22 [Warning] No argument was provided to --log-bin, and
--log-bin-index was not used; so replication may break when this MySQL
server acts as a master and has his hostname changed!! Please use
i actually don't have anything valuable in my database, it's on my
home pc. I upgraded with the standard procedure.
On 6/17/06, Dan Trainor [EMAIL PROTECTED] wrote:
Anthony Ettinger wrote:
I just upgraded to mysql 5, and can't restart the daemon.
060617 11:57:22 [Warning] No argument was
All customer sites will use the same application, but each will have its
own set of 3 databases. In believe the nature of the application
confines users to brief, bursty selects and updates except possibly when
they run reports. I have not specifically analyzed reporting, but I ran
a 2-hour
