UNSOLVED
compress ASM - detail
Hi
Does anyone know how the compress ASM actually works. i.e. some files are not good candidates for compression - datafiles that have actually been compressed already. in this case trying to compress them further would be a waste of processor time & slow the data stream to the tape.
Or is the ASM smarter than that ?
I'm primarily concerned about a couple of Solaris hosts with large file systems containing gzipped database dump files.
Does anyone know how the compress ASM actually works. i.e. some files are not good candidates for compression - datafiles that have actually been compressed already. in this case trying to compress them further would be a waste of processor time & slow the data stream to the tape.
Or is the ASM smarter than that ?
I'm primarily concerned about a couple of Solaris hosts with large file systems containing gzipped database dump files.
- "compressasm does compression - just like most compression tools do"
Gee - Thanks for that !!!
My question was more related to any logic that may exist when the compression ASM processes. I guess its back to directives to selectively implement/skip desired file systems/dirs unfortunately. - The logic is the same as with many other compression tools - no philosophy there - that was my point.
I believe you could play with forget to have compression ignored for files (or extension) you wish to skip having compression applied on.
ble1
6 Operator
•
14354 Posts
•
56186 Points
226
0
Posted April 28th, 2008 03:00
Usually, you use compression on HW side only.. unless you have poor network link and are considering this as temporary solution.