>
> Search speeds and CPU with MyISAM is quite good. I tried InnoDb and insert
> speeds was far too slow because of its row locking versus MyISAM's table
> locking. Some people have been able to fine tune InnoDb but it requires
> even more RAM because InnoDb works best when the entire table fits i
At 12:18 PM 2/5/2007, kalin mintchev wrote:
> Put as much memory in the machine as possible. Building indexes for a
> table
> of that size will consume a lot of memory and if you don't have enough
> memory, building the index will be done on the hard disk where it is 100x
> slower. I've had 100M
> Put as much memory in the machine as possible. Building indexes for a
> table
> of that size will consume a lot of memory and if you don't have enough
> memory, building the index will be done on the hard disk where it is 100x
> slower. I've had 100M row tables without too much problem. However
At 09:44 PM 2/4/2007, kalin mintchev wrote:
hi all...
i just wanted to ask here if somebody has experience in pushing the mysql
limits... i might have a job that needs to have a table (or a few tables)
holding about a 100 million records. that's a lot of records is there
any limitation of s
kalin mintchev" <[EMAIL PROTECTED]>
To: "ViSolve DB Team" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, February 05, 2007 4:07 PM
Subject: Re: mysql limits
thanks... my question was more like IF mysql can handle that amount of
records - about 100 million... and if it's jus
thanks... my question was more like IF mysql can handle that amount of
records - about 100 million... and if it's just a question of cpu power
and memory?
> Hi,
>
> The limit for the table can be set when you create the table itself.
> the MAX_ROWS and AVG_ROW_LENGTH variables (m X n matr
Hi,
The limit for the table can be set when you create the table itself.
the MAX_ROWS and AVG_ROW_LENGTH variables (m X n matrix) will decide the
table size.
MAX_ROWS limts the maximum number of rows in that table. The AVG_ROW_LENGTH
variable decides the length of the row. The specified val
Hi,
Signal 11 can also indicate hardawre problems on BSD. Also FreeBSD
might get you more answers quickly as there are more of us running
FreeBSD with MYSQL for some reason. We runn FreBSD w MySQL/Linux
threads on 4.9 and 5.2 and both work just fine.
Ken
- Original Message -
From: "RV
Let's see if I can give you some ideas.
> -Original Message-
> From: RV Tec [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 18, 2004 8:28 AM
> To: [EMAIL PROTECTED]
> Subject: MySQL limits.
>
> We have a database with approximately 135 tables (MyISAM).
> Most of them are small, but we
Folks, Tim,
Oops! Forgot to mention that... we are running MySQL 4.0.18.
Thanks a lot!
Best regards,
RV Tec
On Tue, 18 May 2004, Tim Cutts wrote:
>
> On 18 May 2004, at 2:28 pm, RV Tec wrote:
>
> >
> > Is MySQL able to handle such load with no problems/turbulences
> > at all? If so, what
On 18 May 2004, at 2:28 pm, RV Tec wrote:
Is MySQL able to handle such load with no problems/turbulences
at all? If so, what would be the best hardware/OS
configuration?
What is the largest DB known to MySQL community?
We regularly run databases with around 200 GB of data per instance,
11 matches
Mail list logo