Hello Darren, Tuesday, May 23, 2006, 11:12:15 AM, you wrote:
DJM> [EMAIL PROTECTED] wrote: >>> Robert Milkowski wrote: >>> >>>> But only if compression is turned on for a filesystem. >>> Of course, and the default is off. >>> >>>> However I think it would be good to have an API so application can >>>> decide what to compress and what not. >>> I agree that an API would be good. However I don't think using the API >>> should allow an application to write compressed data if the file system >>> has that functionality turned off. Its a policy thing if the admin has >>> compression off it is off for a reason. Or maybe what we need is another >>> property value for compression that allows the app to request it but by >>> default we don't do it. >> >> *Only* if we fail to come up with a mechanism to do this properly, >> efficiently automagically. It's not a good idea IMHO. The problem is that with stronger compression algorithms due to performance reasons I want to decide which algorithms and to what files ZFS should try to compress. For some files I write a lot of data even if they are compressing quite good i don't want it - too much CPU would be consumed. However for other files in the same data pool I know we do not write them that often so compression for them would be useful (and cheap in terms of CPU). -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
