network profile
| bio | website | |
|---|---|---|
| location | Yurop | |
| age | ||
| visits | member for | 3 years, 10 months |
| seen | Aug 3 '09 at 3:05 | |
| stats | profile views | 21 |
|
Jul 21 |
comment |
What storage to use for a web file archive? You're right about the access pattern it's almost all reads. I was thinking RAID6 too, although in light of AoE using standard SATA disks perhaps RAID10 is afforable? I have some options to weigh up. Thanks again :-) |
|
Jul 20 |
comment |
What storage to use for a web file archive? Thanks for the answer pauska. varnish/squid plus some application level switching should solve my problem. |
|
Jul 20 |
awarded | Scholar |
|
Jul 20 |
accepted | What storage to use for a web file archive? |
|
Jul 20 |
comment |
What storage to use for a web file archive? Thank you for that edit! What is a few clients BTW, 3 or 300? :-) I have to plan for 100 - 1000 (even when library may not grow) so it seems workload would become more random than sequential especially since they are all clients of varying speeds. In that case I think 14 x SATA disks may not have the random IOPS to keep up? Obviously I have to benchmark this to know for sure but if you have any comments on that I'm interested to hear them :-) |
|
Jul 20 |
comment |
What storage to use for a web file archive? So I could grow the Nexsan SATABeast to 40TB to accomodate the storage requirements, but what about delivery capacity? I think that is the part I'm most confused on. With something like the Sun 7410 I can see options to add SSD cache modules to improve performance. How would I do this in this architecture? Can I have an array of webservers all mounting the same SATABeast, and just load them up with RAM, and keep adding webservers until the disk IO load goes down? |
|
Jul 20 |
awarded | Supporter |
|
Jul 20 |
comment |
What storage to use for a web file archive? Hi, thanks for the answer! I like the sound of this, it sounds easy to expand. I'm curious to know what type of access pattern you can produce 1Gb/s throughput with? e.g. how large is your active/hot fileset and the number of concurrent clients? Obviously 90% clients requesting the same file and 10% requesting different files, most of the load can be delivered from the server's RAM. What if 100 users are all requesting different files? If you did become disk-bound with such configuration, can you add front-end servers (to grow overall RAM availble for caching) ? |
|
Jul 20 |
awarded | Student |
|
Jul 19 |
asked | What storage to use for a web file archive? |
