Re: Performance issues w/ S3

Hi Tink,

Am 21.07.24 um 23:21 schrieb tink via Duplicity-talk:
> And without compression and encryption the local version takes 55 seconds.

The compression and encryption is done by feeding the data into GnuPG 
binary installed on your system.

I suggest following tests:

- use `gpg` and encrypt a file manually and check the timing.

While running following commands my help to find the bottleneck:

`vmstat -w 5`

or

`iostat`

to check I/O wait

`watch ps -p <put pid here> -L -o pid,tid,psr,pcpu,docker,args`

allow to see how the load is spread between threads and which CPU they 
running on. (keep in mind that 100% means full usage of all cores in 
your system. In your case 6.25% means the process is occupying a full core )


Btw. are you running on bare metall or any virtualization?


Bye

  Thomas



Keep in mind, that python by default is not able to take advantage from 
multiple cores. Duplicity has some functionality to share load across 
processes to bypass this limitation, but this still have some boundaries.


>
> On Mon, 22 Jul 2024 at 09:16, tink <[email protected]> wrote:
>
>
>
>     On Mon, 22 Jul 2024 at 08:42, Thomas Laubrock via Duplicity-talk
>     <[email protected]> wrote:
>
>         Hi Tink,
>
>     Hi Thomas,
>
>         Am 21.07.24 um 22:26 schrieb tink via Duplicity-talk:
>         > --no-compression and --no-encryption
>
>         try the switches above for the local backup. Maybe the problem
>         is CPU
>         bound and not I/O bound.
>
>     I'll give it a shot, but think that w/ the recent version of
>     duplicity and concurrency
>     I should get better performance. The machine has 16 cores (HT
>     disabled), 48GB RAM
>     and while duplicity was doing its thing w/ GPG only two cores were
>     busy ...
>
>         Also the timestamps from the log should give an indicator.
>
>         But for me all looks like works as designed. I know, a
>         horrible answer.
>
>     Fair enough, too ;)
>
>
>         Bye
>
>           Thomas
>
>     Bis die Nächte ;)
>     Tink
>
>
>
> -- 
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> _______________________________________________
> Duplicity-talk mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk

_______________________________________________
Duplicity-talk mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk