Re: SSD partitioning
max bianco wrote: 2008/7/22 Rich Emberson [EMAIL PROTECTED]: For a non-laptop machine with the following target characteristics: energy efficient, non-gaming, powerful and fast; should SSDs (http://en.wikipedia.org/wiki/Solid-state_drive) be used and, if so, how? SSD have very fast seek times and can have fast read speeds (http://www.datamarck.com/benchmarks). Specifically, what directories ought to be allocated to the SSD drives? Are you combining a SSD with a regular old HDD? That's what it sounds like. Is there going to be any real performance benefit here? If you have one 7200 rpm and one 1rpm, AFAIK you'll be limited to the 7200 speed. You can only go as fast as your slowest man. Is that not true with SSD? Can you in fact combine them with regular drives without sacrificing performance? -Max If you're doing RAID, you'll get the slowest speed, but that's not what he's talking about. If you put your random-access data on a small, expensive, low-latency device, be it SSD or high-end disk, and put your sequential-access data on a large, cheap, high-latency disk, it'll perform quite nicely, because the sequential access pattern hides the latency of the slow disk quite well. This is why high-end streaming media servers use 7200 RPM SATA drives, even though everything else in the data center is using SAS or Fibre Channel storage. -- Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: SSD partitioning
Rich Emberson wrote: For a non-laptop machine with the following target characteristics: energy efficient, non-gaming, powerful and fast; should SSDs (http://en.wikipedia.org/wiki/Solid-state_drive) be used and, if so, how? SSD have very fast seek times and can have fast read speeds (http://www.datamarck.com/benchmarks). Specifically, what directories ought to be allocated to the SSD drives? Boot (/boot)? All of the bin directories (/bin, /usr/bin, etc. since these are mostly read-only and are used alot)? Lib directories (/lib, /usr/lib, etc.) ? If you are running a database, should at least the index tables be mapped to an SSD? Some of the main tables maybe too big for the current generation ($$) of SSDs. RME SSDs are great at everything except small writes, because you have to re-write an entire 128k block just to set a single 0 bit to a 1 within that block. The new high-capacity Multi-Layer Cell drives are much slower at writes than the more expensive Single-Layer Cell drives, though this is expected to change in the near future as the technology matures. For desktop use, SSDs are great on Linux. For your database, as long as you don't have a lot of small updates going to the SSD, you should be fine. For example, if you have an index that's keyed on something that changes very rarely, and you put that on the SSD, it'll perform very well even if some of the contents of the records themselves (stored on magnetic disk) change frequently. -- Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: SSD partitioning
2008/7/22 Rich Emberson [EMAIL PROTECTED]: For a non-laptop machine with the following target characteristics: energy efficient, non-gaming, powerful and fast; should SSDs (http://en.wikipedia.org/wiki/Solid-state_drive) be used and, if so, how? SSD have very fast seek times and can have fast read speeds (http://www.datamarck.com/benchmarks). Specifically, what directories ought to be allocated to the SSD drives? Are you combining a SSD with a regular old HDD? That's what it sounds like. Is there going to be any real performance benefit here? If you have one 7200 rpm and one 1rpm, AFAIK you'll be limited to the 7200 speed. You can only go as fast as your slowest man. Is that not true with SSD? Can you in fact combine them with regular drives without sacrificing performance? -Max -- If opinions were really like assholes we'd each have just one -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
SSD partitioning
For a non-laptop machine with the following target characteristics: energy efficient, non-gaming, powerful and fast; should SSDs (http://en.wikipedia.org/wiki/Solid-state_drive) be used and, if so, how? SSD have very fast seek times and can have fast read speeds (http://www.datamarck.com/benchmarks). Specifically, what directories ought to be allocated to the SSD drives? Boot (/boot)? All of the bin directories (/bin, /usr/bin, etc. since these are mostly read-only and are used alot)? Lib directories (/lib, /usr/lib, etc.) ? If you are running a database, should at least the index tables be mapped to an SSD? Some of the main tables maybe too big for the current generation ($$) of SSDs. RME -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
