Spindles (Jan 06 2011) |
![]() |
| log in |
Message boards : Technical News : Spindles (Jan 06 2011)
| Author | Message |
|---|---|
|
The informix tweak planned yesterday was postponed and completed today. Why was it postponed? Because the weekly science backup (which happens in the background - doesn't require an outage like the mysql database) wasn't done yet. Normally it takes a few hours. But during major activity it looks like it'll take 10 days! Jeff stopped the ntpckr/rfi processes and that sped things up. | |
| ID: 1064066 · | |
|
Thanks for the update Matt, | |
| ID: 1064067 · | |
|
Matt, thanks for the news! | |
| ID: 1064070 · | |
|
Matt, I do know the new servers are HP Proliants. Which Smart Array controllers does it have and how many? How are the disk arrays and logical drive defined? I have worked with Proliants for many years and could be of help setting up yours!!!! | |
| ID: 1064096 · | |
If returned data is not stored on magnetic tape, you may end up having numerous discs which will have to be swapped in and out depending on have many discs or drives the RAID is able to handle simultaneously. As I understand it, no disks are swapped in and out of the RAID set unless they fail. Drive syncing is expensive on system resources! It just looks like 1 big disk to the file system, that can be scaled to fit the requirements. Drives returning with data from Arecibo are treated exactly in the same way as tapes - as a data source, but cheaper and faster. They are mounted, read and split by the machines responsible for processing the raw data. This working data and project tracking end up on the RAID until purged, with only the results remaining, until those too are archived. | |
| ID: 1065243 · | |
The informix tweak planned yesterday was postponed and completed today. Why was it postponed? Because the weekly science backup (which happens in the background - doesn't require an outage like the mysql database) wasn't done yet. Normally it takes a few hours. But during major activity it looks like it'll take 10 days! Jeff stopped the ntpckr/rfi processes and that sped things up. I am curious Matt, perhaps you or someone could help me understand... While the Science database is too precious to trust to SSD drives, are the access needs mostly "read" or interactive read/write.. and if mostly "read" could the data be mirrored to SSD to speed up the access? Yet again, just a thought. ____________ Janice | |
| ID: 1065256 · | |
As I understand the prices, SSD drives of sufficient size for the database are cost-prohibitive at this time... plus someone would have to donate the SSD drives, or their purchase price! ____________ . | |
| ID: 1065279 · | |
|
A quick trawl says prices, about four times the money for one quarter the space. | |
| ID: 1065297 · | |
Of course I had that thought in mind. But the questions remain, would it work and would it be a good idea? I would cringe at the thought of the base science database being ONLY on such drives. So.. could they be mirrored? ____________ Janice | |
| ID: 1065368 · | |
Matt, I do know the new servers are HP Proliants. Which Smart Array controllers does it have and how many? How are the disk arrays and logical drive defined? I have worked with Proliants for many years and could be of help setting up yours!!!! They are Smart Array P212's - one in each server controlling 12 drives. Both systems are set up the same way: A 2-drive RAID1 mirror (for root), and an 8-drive RAID10 (for data), and 2 global hot spares. - Matt ____________ -- BOINC/SETI@home network/web/science/development person -- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude | |
| ID: 1065392 · | |
|
I think your configuration is based on the standard 256MB onboard cache with 3.5" 1TB 7.2K rpm Hard Drives. As for DB operations are they mostly inserts, selects, or random I/O? | |
| ID: 1065426 · | |
I think your configuration is based on the standard 256MB onboard cache with 3.5" 1TB 7.2K rpm Hard Drives. As for DB operations are they mostly inserts, selects, or random I/O? random I/O - that's what the killer is. When it's sequential we get 200-300MB/sec reads/writes without breaking a sweat. When it's random, it's more like maxed at at 5-10MB/sec. - Matt ____________ -- BOINC/SETI@home network/web/science/development person -- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude | |
| ID: 1065944 · | |
|
Does it have the cache module on the board? From my experience the SmartArrary cards leave something to be desired especially when you load up the number of drives on the card and dealing with DB operations that are typically random in nature. | |
| ID: 1065976 · | |
Does it have the cache module on the board? From my experience the SmartArrary cards leave something to be desired especially when you load up the number of drives on the card and dealing with DB operations that are typically random in nature. Matt: and yes we can shake the collection jar again if things like that will help. It might be close to tax time by the time we get it, but we can do it. ____________ Janice | |
| ID: 1065978 · | |
I think your configuration is based on the standard 256MB onboard cache with 3.5" 1TB 7.2K rpm Hard Drives. As for DB operations are they mostly inserts, selects, or random I/O? can't you enable write cache on raid controllers with a battery backup, which would dramatically improve write performance. but i suppose we don't have real raid controller. i wouldn't enable write cache with only a ups, a server crash can lead to data loss. ____________ | |
| ID: 1068853 · | |
Message boards : Technical News : Spindles (Jan 06 2011)
| Copyright © 2013 University of California |