R3load socket compression

[Former Member]

Does migmon socket option use any compression?

[Former Member]

Yes, 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?

[markus_doehr2]

>

> 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