[Box Backup] child bbstored process ramping up to 100% cpu during bbackupd sync?

[reticent]

This is just based off of observation, i'm just curious if anyone has
experienced this in the past.

The client bbackupd server is a slow USPARC IIi 333mhz with 1.6 gigs of
data that doesn't compress well (audio data).

There are about 350,000 directories and half that amount of files.

The (lazy) sync is painfully slow (somthing like 24 hours).

However what i'm seeing is that during the sync on the backup server
(bbstored) the child process spawned on connection ramps up to 100% cpu
usage as the file that is currently being written increases in size.

Looking as lsof output i can see that there are two files being written
to  by the child process.
(for example): o28.rfw and o28.rfwX
o28.rfw seems to grow according the amount of data that is coming in.
However it seems that the file (and this changes for every new rfw file
that is written) o28.rfwX is constantly being written and deleted.
The strange thing is the file seems to be written up the current size of
o28.rfw and then deleted. So as o28.rfw grows in size the cpu useage
increases evetually using 100% once o28.rfw gets to about 20-30KB.

Backup server is a dual pIII xeon 500mhz with plenty of spare (ecc) memory.


I havn't noticed this when backing up data from other (much faster)
servers.

Has anyone done any benchmarks?
I've been getting really slow rates when backing up/restoring.. 
200-500BPS in the exchange described above.. This is over a local FD 
100M network

Tavis