[ 
https://issues.apache.org/jira/browse/KUDU-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143093#comment-18143093
 ] 

ASF subversion and git services commented on KUDU-3788:
-------------------------------------------------------

Commit 04c5a82dda7629d5b65d03a492145cb6b4b2d872 in kudu's branch 
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=04c5a82dd ]

KUDU-3788 use parallel compress/decompress for xz

Kudu's 3rd-party pre-built artifact tarballs are compressed with
xz/libzma to achive better compression ratio.  Naturally, it takes a lot
of CPU cycles to compress and decompress those (especially the former).
Since the OSes/distros supported by Kudu as of today have xz/lzma of
5.2.0 and newer versions, let's use available CPU cores for compression
and decompression, when applicable.

Change-Id: I9000f1d9bc09c70415e22983f80f7dd50ebe031f
Reviewed-on: https://gerrit.cloudera.org/25409
Reviewed-by: Marton Greber <[email protected]>
Tested-by: Marton Greber <[email protected]>


> Allow fethcing and using pre-built 3rd-party components when building Kudu
> --------------------------------------------------------------------------
>
>                 Key: KUDU-3788
>                 URL: https://issues.apache.org/jira/browse/KUDU-3788
>             Project: Kudu
>          Issue Type: Improvement
>            Reporter: Alexey Serbin
>            Assignee: Alexey Serbin
>            Priority: Major
>             Fix For: 1.19.0
>
>
> It would be nice to allow to fetch and use pre-built 3rd-party components 
> when building Kudu.  Each of the 3rd-party components should be checked 
> against a presence of pre-built version that matches the machine architecture 
> and OS, and the matching rule should compare at least the following 
> attributes:
> * Component name (e.g., gflags)
> * Component version (minor, major, patch, or just source hash if no semantic 
> versioning is available)
> * The machine's CPU architecture that binaries/libraries are built for (e.g., 
> x86_64, arm64)
> * OS name or flavor/distro name if applicable (e.g., macOS, Ubuntu, Debian, 
> RHEL, etc.)
> * OS version: major, minor (e.g., 9.1 for RHEL, 24.04 for Ubuntu, 15.7 for 
> macOS, etc.)
> * The toolchain that the bits are built with: compiler name, major and minor 
> versions, and the standard C++ library flavor where applicable (e.g., 
> gcc-10.5-libstdc++, clang-15.0)
> * Sanitizer option: TSAN if built with tread sanitizer support, or none if a 
> regular build



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to