duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Duplicity 4.2.1 on CentOS 4.7 causing resource sho


From: Marcus Clements
Subject: Re: [Duplicity-talk] Duplicity 4.2.1 on CentOS 4.7 causing resource shortage on VPS
Date: Thu, 5 Mar 2009 16:06:47 +0100

2009/3/5 Kenneth Loafman <address@hidden>:
> Marcus Clements wrote:
>> There certainly is a spike in the number of processes when the backup runs:
>> http://brightonart.eu/images/processes-week.png
>>
>> Marcus
>>
>> 2009/3/4 Douglas Muth <address@hidden>:
>>> On Wed, Mar 4, 2009 at 11:48 AM, Marcus Clements
>>> <address@hidden> wrote:
>>>> I'm not surprised to hear grumbles about Dreamhost, the service seems
>>>> pretty awful, but I'm interested to understand how the target server
>>>> affects memory resource use on the originating server.
>>>>
>>> Yeah, I guess I should have elaborated on that. :-)
>>>
>>> My experience with Dreamhost specifically revolved around massive
>>> amounts of I/O wait.  Like, doing an "ls -l" would take some seconds,
>>> and writing a file to disk would take even longer.
>>>
>>> One possibility is that if Dreamhost were taking forever to write
>>> files, the data to be written could be "piling up" on the source
>>> machine, and causing the spike in memory. Not knowing the internals of
>>> Duplicity, I could also be flat out wrong. :-)  Maybe the author of
>>> Duplicity could shed some light on this idea.
>
> It's not piling up on the source machine unless you're using the
> experimental --asyncronous-upload option.  Even then, it would only save
> one volume ahead of the network, but not in memory, on disk, so not much
> there to worry about.
>
> I'm not sure what's running that would cause the problem.  I've done
> some googling on 'simfs', but don't see anything.  Do you know what
> virtualization software they use?
>
> ...Ken
>
>
Virtuozzo
The control panel version info:
Virtuozzo Power Panels

Version 16.10.swsoft (build: 3.0.0-16.10.swsoft)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]