Am 19.02.2011 16:59, schrieb Bryan Cantwell:
> I have an innodb table with 200 million rows and growing.
more interesting is the db-size!
> innodb_buffer_pool_size = 768M
roo small, in the best case it is as large as the database
or so large as pissoble to avoid swapping
> innodb_log_file_size
1. Which version of MySQL? Judging from your my.cnf it's not MariaDB 5.2 or
Percona Server? They have very good enhancement, particularly in the high
concurrency innodb atmosphere. InnoDB is a lot more tunabl;e in those
versions. Switching from a stock mysql version is adrop-in replacement, so
if t
I have an innodb table with 200 million rows and growing.
It is a highly active table with tons of inserts and updates at all times.
I notice a select query I test on that table is 0.01 seconds or less
when all the inserts/updates are OFF.
But when I throttle up the writes to the table, the selec
Hello world,
I'm pretty new at SQL. I'm just trying to build a simple document
index. I'm hoping there is a better way to do things than what I've
got here.
Here's what I've got for a table definition:
>mysql> create table main_index(
> sequence int unsigned primary key auto_increment n
Philip,
InnoDB does not give an exact number of rows
to the query analyzer. A problem is that
in a multiversioned database different transactions
will see a different number of rows in the table,
and a single count of rows cannot be kept.
It is an eternal problem in query optimization.
Errors in
I've got a table with roughly 1 rows that's being joined with
several other tables Ten-thousand rows isn't a whole lot, but it makes
a difference. With MyISAM, the query is optimized perfectly, exactly
how I would expect it to be optimized given our indexing scheme, but
when I switch the tab
Hi,
I have a perl script that loops through and executes 2 queries 50
times. I need to make sure that I have done all I can to make these
queries and the indexing on the table as efficient as possible.
Would someone do me the gargantuan favor of taking a peek at the info
below and offer any sug
Ok, since my quries aren't responding, I've been told to drop the table, create the
table again, and then import the data. The only index on the table is the primary key.
Will it help to add an index for every column to optimize the table? I have queries
that pull data from different columns on
