Same custy as last post....
Before I go off into researching and stat checking , I wonder if someone
has a quick answer
Oracle DB redo log dataset is compressed (don;t ask, DBAs changed usage without saying).
log files show as 250Mb in OraDB and 100Mb on filesystem .... DBAs don;t
like this (banging head against wall).
Anyway,they did some copy tests.
With compression on a log file takes 2mis 45 secs (about 1min 45 sec in kernel) to copy.
With compression off, 15 secs.
That is an excessive over head IMO.
Server is M4000, S10. Zpool version =37.
I'll try and get a comparable test on the new S7s tomorrow.... just
don;t want to be wasting time on what I see as a non issue (ie :- just
turn compression off).
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! https://www.libreoffice.org/
On Wednesday, January 15, 2020 at 2:58:54 PM UTC-7, YTC#1 wrote:
Same custy as last post....
Before I go off into researching and stat checking , I wonder if someone
has a quick answer
Oracle DB redo log dataset is compressed (don;t ask, DBAs changed usage
without saying).
log files show as 250Mb in OraDB and 100Mb on filesystem .... DBAs don;t
like this (banging head against wall).
Anyway,they did some copy tests.
With compression on a log file takes 2mis 45 secs (about 1min 45 sec in
kernel) to copy.
With compression off, 15 secs.
That is an excessive over head IMO.
Server is M4000, S10. Zpool version =37.
I'll try and get a comparable test on the new S7s tomorrow.... just
don;t want to be wasting time on what I see as a non issue (ie :- just
turn compression off).
Hi Bruce,
Which ZFS compression is this? According to our recommendations, the only compression recommended for Oracle DB workloads is for the archive.
https://www.oracle.com/technetwork/server-storage/solaris10/config-solaris-zfs-wp-167894.pdf
Same custy as last post....
Before I go off into researching and stat checking , I wonder if someone
has a quick answer
Oracle DB redo log dataset is compressed (don;t ask, DBAs changed usage without saying).
log files show as 250Mb in OraDB and 100Mb on filesystem .... DBAs don;t
like this (banging head against wall).
Anyway,they did some copy tests.
With compression on a log file takes 2mis 45 secs (about 1min 45 sec in kernel) to copy.
With compression off, 15 secs.
That is an excessive over head IMO.
Server is M4000, S10. Zpool version =37.
I'll try and get a comparable test on the new S7s tomorrow.... just
don;t want to be wasting time on what I see as a non issue (ie :- just
turn compression off).
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! https://www.libreoffice.org/
On Wednesday, January 15, 2020 at 2:58:54 PM UTC-7, YTC#1 wrote:
Same custy as last post....ZFS compresses blocks. After compression is disabled, then its possible that the redo log will contain both compressed and uncompressed blocks until its rotated completely.
Before I go off into researching and stat checking , I wonder if someone
has a quick answer
Oracle DB redo log dataset is compressed (don;t ask, DBAs changed usage
without saying).
log files show as 250Mb in OraDB and 100Mb on filesystem .... DBAs don;t
like this (banging head against wall).
Anyway,they did some copy tests.
With compression on a log file takes 2mis 45 secs (about 1min 45 sec in
kernel) to copy.
With compression off, 15 secs.
That is an excessive over head IMO.
Server is M4000, S10. Zpool version =37.
I'll try and get a comparable test on the new S7s tomorrow.... just
don;t want to be wasting time on what I see as a non issue (ie :- just
turn compression off).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 82:53:24 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,333,520 |
Posted today: | 1 |