R3load SocR3load socket compressionket Compression
-
Upload
suwatchai-manchansa -
Category
Documents
-
view
12 -
download
0
description
Transcript of R3load SocR3load socket compressionket Compression
-
Generated by Jive on 2014-06-10+02:001
R3load socket compression
Daniyar Zhussupbayev 2 posts since Oct 18, 2009R3load socket compression Oct 8, 2010 3:13 PMDoes migmon socket option use any compression?
Markus Doehr 18,673 posts since Mar 21, 2004Re: R3load socket compression Oct 8, 2010 6:03 PM>
Daniyar Zhussupbayev wrote:
> Does migmon socket option use any compression?
Not sure what you mean.
The R3load data itself is compressed (it's about 1/10 of the original size). There's no other compression used.
Markus
Daniyar Zhussupbayev 2 posts since Oct 18, 2009Re: R3load socket compression Oct 8, 2010 6:29 PMYes, if option "net" is used (dump files are written to disk) - then export is compressed 1/10.
If I use option "socket" - there are no dump files.Parallel export/import of 1 TB database take ~5 hours.Bandwidth usage monitor shows load 580 Mb/s from 1Gb/s. It is ~250GB/hour.It seems that R3load process with "-socket" option doesn't compress data.
Now I'm going to use parallel export/import with "net" option instead.Simple source DB export takes just 1 hour, that is export speed is 1TB/hour.It will create dumps with speed 100GB/hour.Transferring 100GB over 1Gb/s channel will take less than an hour.
But may be there is a option, that can force R3load to use compression with "socket" option?