-->-----Original Message----- -->From: Mysql List [mailto:[EMAIL PROTECTED] -->Sent: Thursday, July 24, 2003 10:47 AM -->To: Dathan Vance Pattishall -->Cc: [EMAIL PROTECTED] -->Subject: Re: Huge Server configuration --> -->Dathan Vance Pattishall wrote: --> -->Only for read with lots of filtering. Sorting is not a priority. Only -->for retreiving data with multiple conditions. -->some of the fields are indexed. some of them are not. but those will -->also be used in the where condition. --> -->>Reason by example: -->>Sun T3 with 7 drives. I'm IO bound with a read heavy 2 Gb where most of -->>the data is in memory. I'm transferring 15MB a second of read traffic.
I do a fair amount of writes and reads about 40/60 ratio something mysql is not very good at. Thus the need for many flushes to the disk and disk grabs. With this inevitability, this causes my RAID array to transfer a lot of data so much so I'm hitting the arrays max throughput which is about 15MB/sec or 140Mbits a second. With your primarily read box you still might be IO bound especially during table scans. Try using the query cache. As long as you don't write to the mysql cached data it should be a win for you. -->> -->> -->Please explain. --> -->Thanks Again -->Chandra -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
