Anil Doppalapudi wrote:
ours is InnoDB. we are not getting any performance problems with the
settings. it is working fine since last 1 Year. to my knowledge due to
myisam type you are getting performance issue.
Thanks
Anil
based on this email list, myisam is prefered for heavy query/index use,
22, 2004 7:12 PM
To: Anil Doppalapudi
Cc: mysql@lists.mysql.com
Subject: Re: Restore help! been going 2 weeks
Those are pretty much standard settings
I had ours set almost exactly like that, and performance was worse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
Those are pretty much standard settings
I had ours set almost exactly like that, and performance was worse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
t: Monday, December 20, 2004 5:56 PM
To: matt_lists
Cc: Anil Doppalapudi; [EMAIL PROTECTED]
Subject: Re: Restore help! been going 2 weeks
matt_lists wrote:
> Can you post your my.ini or my.cnf
>
> sense your restore actually worked
>
> Mine is not swapping, in fact, mysql is only usi
matt_lists wrote:
matt_lists wrote:
Can you post your my.ini or my.cnf
sense your restore actually worked
Mine is not swapping, in fact, mysql is only using 610,824 K of ram,
there is still over 1 gig of ram free
Our next server will have 16 gig of ram and quad xeons, I'm going to
completely dis
matt_lists wrote:
Can you post your my.ini or my.cnf
sense your restore actually worked
Mine is not swapping, in fact, mysql is only using 610,824 K of ram,
there is still over 1 gig of ram free
Our next server will have 16 gig of ram and quad xeons, I'm going to
completely disable the swap file
Can you post your my.ini or my.cnf
sense your restore actually worked
Mine is not swapping, in fact, mysql is only using 610,824 K of ram,
there is still over 1 gig of ram free
Our next server will have 16 gig of ram and quad xeons, I'm going to
completely disable the swap files
--
MySQL Genera
: matt_lists [mailto:[EMAIL PROTECTED]
Sent: Friday, December 17, 2004 12:11 AM
To: Anil Doppalapudi
Cc: [EMAIL PROTECTED]
Subject: Re: Restore help! been going 2 weeks
Anil Doppalapudi wrote:
>it is not normal. i have restored 90 GB database in 2 days on dell server
>with 2 GB RAM.
>Are
Are you sure innodb is better for tables larger than 4 gig?
| 12 | xotech | localhost:3115 | finlog | Query | 238224 | copy to tmp
table | alter table bragg_stat engine=innodb pack_keys=0 |
| 14 | xotech | localhost:3356 | NULL | Query | 0 |
NULL |
is going on
then check your my.cnf parameters.
Anil
-Original Message-
From: matt_lists [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 16, 2004 6:15 PM
To: [EMAIL PROTECTED]
Subject: Re: Restore help! been going 2 weeks
The restore is still running
is this normal? How do you all d
The restore is still running
is this normal? How do you all deal with customers that do not have
their data for almost 3 weeks, and no end in sight
I've had oracle crashes before, the restores were very simple, this is not
I am very disappointed with mysql's performance with files over 5 gig
Alm
Almost all my MYD files are more than 4 gig
I was not aware of this limitation
I tested with InnoDB and found it horribly slow for what we do
Anil Doppalapudi wrote:
check your .myd file size. if table type is myisam and it it is more than 4
GB then convert it to InnoDB.
--Anil
--
MySQL Genera
check your .myd file size. if table type is myisam and it it is more than 4
GB then convert it to InnoDB.
--Anil
-Original Message-
From: matt_lists [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 14, 2004 8:36 PM
Cc: [EMAIL PROTECTED]
Subject: Re: Restore help! been going 2 weeks
Nobody else has problems with restores on 8+ gig tables?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
14 matches
Mail list logo
