2
edits
Jwentwistle (talk | contribs) (added link to white paper) |
|||
Line 11: | Line 11: | ||
* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites. | * [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites. | ||
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre. | ** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre. | ||
** [http://en.wikipedia.org/wiki/POSIX | ** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster. | ||
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB. | ** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB. | ||
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software. | ** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software. |
edits