tag:blogger.com,1999:blog-6485859219631902178.post8044184676721078820..comments2024-01-09T02:22:16.867-08:00Comments on Dave Simpson's Storage Blog: The drawbacks to data reductionDave Simpsonhttp://www.blogger.com/profile/06706419354444528272noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6485859219631902178.post-91188899450208094102009-07-10T15:01:56.751-07:002009-07-10T15:01:56.751-07:00Interesting post, Dave. Here are a few thoughts, a...Interesting post, Dave. Here are a few thoughts, as expressed by a few of the folks at Ocarina.<br /><br /> 1. Although there’s lots of talk about filer performance, very few applications push that envelope. Where they do, in-band solutions are the way to go. But for most storage admins, efficiency is a higher priority than maximizing performance.<br /> 2. There’s no disputing the data aging curve; after a couple days of inactivity, IO requirements on a given file drop dramatically. As long as the post-process reduction solution includes basic filters and policies, this can be precisely tuned to minimize or eliminate performance impact.<br /><br />Although we like the benefits the post-processing architecture because of its more powerful impact on large data-stores, the important trend to watch will be end-to-end optimization, where the movement of data between tiers, across the WAN, and to backup solutions doesn’t require wasteful rehydration and re-assembly of files.<br /><br />For more on this, Carter George has written a post that follows up: http://onlinestorageoptimization.com/index.php/dedupe-for-online/<br /><br />Thanks,<br />Sunshine MugrabiSunshinehttps://www.blogger.com/profile/07355540035019363654noreply@blogger.com