On 9/25/2018 5:18 AM, George Anchev via Bacula-users wrote:
...
Also: I would like to use a faster machine to
create builds for other slower machines (one of
them even 32-bit). Do I need anything more than
just finding the proper "-march" setting for the
target CPU?
I'm not sure you need to do even that. The default
should be to produce code that will run on all
supported CPUs (of the same instruction set
architecture). Unless you need to cross-compile, or
to target a CPU so old that it is no longer
supported by default (e.g., a 80x86 with x<6), you
probably don't need to do anything special. Creating
a 32-bit build on a 64-bit system may require you to
use -m32 (or whatever the exact syntax is) or (my
preferred approach) to build in a 32-bit environment
(chroot, container or virtual machine).
I am particularly interested in building FDs for two
types of CPUs. I am attaching the /proc/cpuinfo for
both. Could you advise on specifics?
I'm not sure whether compiler optimizations will make a huge difference.
The FD is quite i/o bound, in general. However, there are exceptions. On
clients with weak CPUs, enabling compression and/or encryption will very
much affect performance. If software compression is required, then try
to use LZO. Weak clients will usually perform better with compression
disabled, in spite of the increased network traffic.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
