How to really get the most out of your SAS disk arrays. This may surprise you how to tweak it out!

Поділитися
Вставка
  • Опубліковано 28 лип 2024
  • This video talks to the nature of how SAS connections are broken up in channels and how to take advantage of that for the best disk groupings. BTW Channel busing is how SAS connections allow for group access to disk by three channels. This is what you can do in the video to see how to tweak out that last bit of disk speed from your arrays. Enjoy!
  • Наука та технологія

КОМЕНТАРІ • 9

  • @goolom
    @goolom Рік тому +2

    Great video!
    Not sure if this is your area of focus - but would be great if you can do a video on 'noise control' for those of us that must have a server in our office or apartment (yikes) - I am stuck with the Rosewill LSV-4500 because the super micro's (even with quiet attachments) are very very loud.
    Would be great if you can maybe do a video on DIY or alternatives that are 'quiet'.
    Very cool channel!

    • @leadiususa7394
      @leadiususa7394  Рік тому

      Oh yes that is part of it. Disk arrays (either SSD or spinning disk it doesn't matter...) control their own fan output so the trick this is to place the array close to the lowest point near a AC ducking or vent, the better the air flow the lower the fans will run. You may want to go with a 2U server instead and can be throttle down in the BIOS to run silent and limit the number of disks you use to keep the temp down inside the case. The server case will get loader it it gets hot and will not be silent for long. Hope this helps some... /:>

  • @Nickle314
    @Nickle314 Рік тому +1

    I understand RAID etc. However using a disk array for backup. Can you have drives stop if they haven't been accessed for a given period of time? Perhaps with the directory information on a SSD?

    • @leadiususa7394
      @leadiususa7394  Рік тому +1

      Well yes the controller can spin down disks after a period of time that you set plus I think also TrueNAS will let you do that as well at the OS level. No need to use SSD for directory for you have RAM caching to do that role. SSD drives do not spin down or go to sleep. No need.

    • @Nickle314
      @Nickle314 Рік тому +1

      @@leadiususa7394 On the TrueNAS thanks - I'll do some research based on the hints.
      On the SSD, let me clarify. They don't spin down. So the question was can you have the directory info for the HDD that have spun down, on the SSD. That way you don't have to start the drive up to do a dir listing, or find out space that's available. It's only if you want to read or write the contents of a file on the drive, that you need to spin it up.
      Now I know some drives have SSDs for cache to aid in this

    • @leadiususa7394
      @leadiususa7394  Рік тому

      @@Nickle314 You have it about right. The caching is controlled by the OS/controller level and can use RAM or SSD or both as needed and it holds many values (Data info) including the Directory tree and other values. All data will first go to the cache first and when it is filling up it will active the SSD drives to write or read as need so yes that means the SSD drive are in a normal passive state until call for use. But! Did you know that SSD drives use more power then spinning disks on avg. draws during use. Oh and as a side note yes, SSD drives do have a kinda spin up state (Like spinning drive have when spinning their disks.) but is done base on voltage instead of RPMs like the spinning disk have. Over all the ware and tear is the same for both SSD and spinning disks over time. That is how the Hard Drive companies stay in business. Sad I know.. Back in the day I remember the 15K RPM 15 year life cycle hard drives, Those things work for a very long time. But there is no money in that way of business! Next!

    • @Nickle314
      @Nickle314 Рік тому +1

      @@leadiususa7394 Ages ago I came across an IBM mainframe set up.
      RAM -> slow ram -> Fast disks -> Slow disks -> tape [a robot carosel] was the heirarchy.
      Files slowly went down the stack if not accessed, and then if they were, slowly move up the heirarchy.
      There was some config, such as how far up the stack things moved when accessed, but its a LRU strategy in practice.
      You can imagine similar for onsite offsite, remote back up and RAID.
      What's needed is just set the policy and let the machine sort it out for you.
      I'll have to check that SSD start up power consumption. I've not heard that.

    • @leadiususa7394
      @leadiususa7394  Рік тому +1

      @@Nickle314 Yes that is correct. We call it HSM now (Hierarchical Storage Management) except you can now use Cloud tech to act as the cheap slower speed storage. Or you cna use a local SSD for the high speed needs and SAS or SATA or both as your slow HSM storage if you don't want to use cloud storage. Not to many people need that kind of storage at home for a DB or Application needs. Most just store data and want to get data over faster so they go SSD way. /:> But some do build out test run with applications and there own data bases. So go for it! The cool thing is that you can do it by buying cheap stuff off EBay to do it. Sweet!
      Enjoy dude!