Re: [Bacula-users] Encryption times [SEC=UNCLASSIFIED]

2011/6/9 Ansgar Konermann <ansgar.konermann AT googlemail DOT com>

Am 09.06.2011 19:57, schrieb Steve Ellis:
I do know that encryption runs on the client and, I believe, is single-threaded
Not sure if it's actually "single-threaded", but I can say for sure that it does not make full use of all cores of a multi-core processor.

Well, when backup job starts bacula file daemon starts two new threads: a working thread and a watchdog thread. A working thread is responsible for all backup procedures. It finds a next file, read, performs an md5 digest, compression, encryption, backup stream serialization and sends into SD. Step by step in one thread, at 64kB block size. This is a main bottleneck for slow backup speed.

regards

--
Radosław Korzeniewski
radoslaw AT korzeniewski DOT net

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread]	Current Thread	[Next in Thread>
[Bacula-users] Encryption times [SEC=UNCLASSIFIED], Alan Langley Re: [Bacula-users] Encryption times [SEC=UNCLASSIFIED], Steve Ellis Re: [Bacula-users] Encryption times [SEC=UNCLASSIFIED], Ansgar Konermann Re: [Bacula-users] Encryption times [SEC=UNCLASSIFIED], Radosław Korzeniewski <=