Re: hypothetical question about data storage

2013-07-30 Thread Carsten Pedersen
On 30-07-2013 01:16, Rick James wrote: Elevator... If the RAID _controller_ does the Elevator stuff, any OS optimizations are wasted. And there have been benchmarks backing that up. (Sorry, don't have any links handy.) RAID 5/10 ... The testing I have done shows very little difference.

Re: hypothetical question about data storage

2013-07-30 Thread Manuel Arostegui
2013/7/30 Rick James rja...@yahoo-inc.com Elevator... If the RAID _controller_ does the Elevator stuff, any OS optimizations are wasted. And there have been benchmarks backing that up. (Sorry, don't have any links handy.) RAID 5/10 ... The testing I have done shows very little

RE: hypothetical question about data storage

2013-07-30 Thread Johan De Meersman
Rick James rja...@yahoo-inc.com wrote: When writing a random block, RAID-5 does not need to touch all the drives, only the one with parity. Suitable XORs will update it correctly. So, a write hits 2 drives, whether you have RAID-5 or -10. Only if the other blocks happen to be in the cache,

RE: hypothetical question about data storage

2013-07-29 Thread Rick James
] Sent: Saturday, July 27, 2013 4:32 AM To: mysql@lists.mysql.com Subject: Re: hypothetical question about data storage On 7/26/2013 6:58 PM, Chris Knipe wrote: The issue that we have identified is caused by seek time - hundreds of clients simultaneously searching for a single file

RE: hypothetical question about data storage

2013-07-29 Thread Johan De Meersman
Rick James rja...@yahoo-inc.com wrote: For MySQL + RAID, a Linux elevator strategy of 'deadline' or 'noop' is optimal. (The default, 'cfq', is not as good.) I should look into those again at some point. Do you have a brief word as to why they're better? A RAID controller with multiple drives

RE: hypothetical question about data storage

2013-07-29 Thread Rick James
James; will...@techservsys.com; mysql@lists.mysql.com Subject: RE: hypothetical question about data storage Rick James rja...@yahoo-inc.com wrote: For MySQL + RAID, a Linux elevator strategy of 'deadline' or 'noop' is optimal. (The default, 'cfq', is not as good.) I should look into those

Re: hypothetical question about data storage

2013-07-27 Thread william drescher
On 7/26/2013 6:58 PM, Chris Knipe wrote: The issue that we have identified is caused by seek time - hundreds of clients simultaneously searching for a single file. The only real way to explain this is to run 100 concurrent instances of bonnie++ doing random read/writes... Your disk utilization

Re: hypothetical question about data storage

2013-07-26 Thread Johan De Meersman
, 2013 11:53:53 PM Subject: hypothetical question about data storage Hi all, We run an VERY io intensive file application service. Currently, our problem is that our disk spindles are being completely killed due to insufficient SEEK time on the hard drives (NOT physical read/write speeds

Re: hypothetical question about data storage

2013-07-26 Thread Chris Knipe
question about data storage Hi all, We run an VERY io intensive file application service. Currently, our problem is that our disk spindles are being completely killed due to insufficient SEEK time on the hard drives (NOT physical read/write speeds). We have an directory structure where

RE: hypothetical question about data storage

2013-07-26 Thread Rick James
26, 2013 12:30 AM To: Johan De Meersman Cc: mysql Subject: Re: hypothetical question about data storage Hi All, Thanks for the responces, and I do concur. I was taking a stab in the dark so to speak. We are working with our hosting providers currently and will be introducing

RE: hypothetical question about data storage

2013-07-26 Thread Johan De Meersman
- From: ckn...@savage.za.org [mailto:ckn...@savage.za.org] On Behalf Of Chris Knipe Sent: Friday, July 26, 2013 12:30 AM To: Johan De Meersman Cc: mysql Subject: Re: hypothetical question about data storage Hi All, Thanks for the responces, and I do concur. I was taking a stab

Re: hypothetical question about data storage

2013-07-26 Thread Chris Knipe
- From: ckn...@savage.za.org [mailto:ckn...@savage.za.org] On Behalf Of Chris Knipe Sent: Friday, July 26, 2013 12:30 AM To: Johan De Meersman Cc: mysql Subject: Re: hypothetical question about data storage Hi All, Thanks for the responces, and I do concur. I was taking a stab in the dark

Re: hypothetical question about data storage

2013-07-26 Thread hsv
2013/07/27 00:58 +0200, Chris Knipe I would definately consider the md5 checksum as a PK (char(32) due to the hex nature), Well, not that it greatly matters, but you could convert it to BINARY(16). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:

hypothetical question about data storage

2013-07-25 Thread Chris Knipe
Hi all, We run an VERY io intensive file application service. Currently, our problem is that our disk spindles are being completely killed due to insufficient SEEK time on the hard drives (NOT physical read/write speeds). We have an directory structure where the files are stored based on the

Re: hypothetical question about data storage

2013-07-25 Thread Vahric Muhtaryan
Hi, Sorry but mysql is not the address of it , use riak instead of mysql With riak which is key and value based , all keys are on memory and just only one seek enough to handle it Consider to use riak VM On 7/26/13 12:53 AM, Chris Knipe sav...@savage.za.org wrote: Hi all, We run an VERY io