Comments on: Umm, Why Is Hoosier Access Taking Forever to Load? http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/ HoosierAccess.com Tue, 14 Oct 2008 06:04:51 +0000 http://wordpress.org/?v=2.6.1 By: Adam Longworth http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2221 Adam Longworth Thu, 27 Mar 2008 21:17:45 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2221 ....and I just happen to be a great big dork.... ….and I just happen to be a great big dork….

]]> By: Adam Longworth http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2213 Adam Longworth Thu, 27 Mar 2008 18:52:41 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2213 Mud? What mud--I feel like I'm the high-school jock lost in a dungeons and dragons convention... Mud? What mud–I feel like I’m the high-school jock lost in a dungeons and dragons convention…

]]> By: Josh Gillespie http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2212 Josh Gillespie Thu, 27 Mar 2008 17:37:25 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2212 Thanks for laymans interpretation at the end of your explanation. I was lost a bit. As for our webmaster, he's there on business for the company he works for which is based here in Indianapolis. He'll be returning this weekend. Don't worry, we're not going to export that job! Thanks for laymans interpretation at the end of your explanation. I was lost a bit.

As for our webmaster, he’s there on business for the company he works for which is based here in Indianapolis. He’ll be returning this weekend.

Don’t worry, we’re not going to export that job!

]]> By: Nathan Brindle http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2211 Nathan Brindle Thu, 27 Mar 2008 17:34:09 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2211 RAID 6 stripes data across multiple (mirrored) disks, and calculates parity for added redundancy and stores parity information across one set of stripes. RAID 6 is highly fault-tolerant as a result; if a disk fails, you pull it, put in a new one, and the array is rebuilt without losing data. What makes RAID 6 slow is the need to calculate parity on write operations. RAID 10 (aka RAID 1+0) also stripes your data across multiple (mirrored) disks, but without parity. Without parity, there is an "acceptable" level of fault-tolerance as long as failed disks are replaced promptly, and since there's no parity calculation, the configuration is quite fast. Under RAID 10, if you lose all of the disks in a single mirror array, you lose all of your data across the entire stripe set. With RAID 6, even if you lose all the disks in the mirror, it can still be rebuilt from the remaining disks by using the parity bits. In other words, you're been moved to a faster but somewhat less fault-tolerant configuration. I'd call this a reasonable tradeoff. But why in the world is your webmaster in China? :) RAID 6 stripes data across multiple (mirrored) disks, and calculates parity for added redundancy and stores parity information across one set of stripes. RAID 6 is highly fault-tolerant as a result; if a disk fails, you pull it, put in a new one, and the array is rebuilt without losing data. What makes RAID 6 slow is the need to calculate parity on write operations.

RAID 10 (aka RAID 1+0) also stripes your data across multiple (mirrored) disks, but without parity. Without parity, there is an “acceptable” level of fault-tolerance as long as failed disks are replaced promptly, and since there’s no parity calculation, the configuration is quite fast.

Under RAID 10, if you lose all of the disks in a single mirror array, you lose all of your data across the entire stripe set. With RAID 6, even if you lose all the disks in the mirror, it can still be rebuilt from the remaining disks by using the parity bits.

In other words, you’re been moved to a faster but somewhat less fault-tolerant configuration. I’d call this a reasonable tradeoff.

But why in the world is your webmaster in China? :)

]]> By: Josh Gillespie http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2205 Josh Gillespie Thu, 27 Mar 2008 15:00:38 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2205 The quickness leads me to believe that the transfer is either completed or near completion. Here's hoping so. The quickness leads me to believe that the transfer is either completed or near completion. Here’s hoping so.

]]> By: Chris http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2203 Chris Thu, 27 Mar 2008 02:16:11 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2203 The site seems to be loading pretty quickly right now. It will be interesting to see it when it's up and running on the new servers! The site seems to be loading pretty quickly right now. It will be interesting to see it when it’s up and running on the new servers!

]]> By: Josh Gillespie http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2200 Josh Gillespie Wed, 26 Mar 2008 19:50:03 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2200 Yep, exactly what I thought. Yep, exactly what I thought.

]]> By: Adam Longworth http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2198 Adam Longworth Wed, 26 Mar 2008 19:37:22 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2198 clear as mud... clear as mud…

]]> By: Brian Sikma http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2196 Brian Sikma Wed, 26 Mar 2008 19:01:04 +0000 http://hoosieraccess.com/blog/2008/03/26/umm-why-is-hoosier-access-taking-forever-load/#comment-2196 Thanks for whatever that means. Thanks for whatever that means.

]]>