HAST initial sync speed

[Thomas Steen Rasmussen]

On 11-08-2010 00:14, Thomas Steen Rasmussen wrote:
> On 10-08-2010 09:55, Pawel Jakub Dawidek wrote:
>> It does make sense, but HAST is not doing this:) Could you start with
>> veryfing if synchronization is so slow also when you have only one
>> resource configured?
>>
>
> I can now confirm that synchronization is also slow with only one HAST 
> resource.
> It is currently running with 2.5 megabits per second... around 
> 300kilobytes per sec
> is written to the disk according to gstat.
> An iperf test shows a network potential of about a gigabit (wire speed).
>
Just a quick update, it is still working on syncing the one HAST 
resource configured
the other day:

[root at server1 ~]# date && hastctl status
Thu Aug 12 14:11:18 CEST 2010
hasthd4:
   role: primary
   provname: hasthd4
   localpath: /dev/label/hd4
   extentsize: 2097152
   keepdirty: 64
   remoteaddr: 192.168.0.15
   replication: memsync
   status: complete
   dirty: 102651396096 bytes
[root at server1 ~]# date && hastctl status
Fri Aug 13 09:48:06 CEST 2010
hasthd4:
   role: primary
   provname: hasthd4
   localpath: /dev/label/hd4
   extentsize: 2097152
   keepdirty: 64
   remoteaddr: 192.168.0.15
   replication: memsync
   status: complete
   dirty: 80425779200 bytes

Just under 20 gigabytes in just under 20 hours.

Any suggestions are appreciated,

Thomas Steen Rasmussen