Return-Path: X-Original-To: apmail-tez-issues-archive@minotaur.apache.org Delivered-To: apmail-tez-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD06418804 for ; Wed, 8 Jul 2015 15:39:04 +0000 (UTC) Received: (qmail 97839 invoked by uid 500); 8 Jul 2015 15:39:04 -0000 Delivered-To: apmail-tez-issues-archive@tez.apache.org Received: (qmail 97783 invoked by uid 500); 8 Jul 2015 15:39:04 -0000 Mailing-List: contact issues-help@tez.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tez.apache.org Delivered-To: mailing list issues@tez.apache.org Received: (qmail 97773 invoked by uid 99); 8 Jul 2015 15:39:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2015 15:39:04 +0000 Date: Wed, 8 Jul 2015 15:39:04 +0000 (UTC) From: "Tsuyoshi Ozawa (JIRA)" To: issues@tez.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (TEZ-2605) [Umbrella] CPU optimizations for hotspots MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TEZ-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated TEZ-2605: -------------------------------- Description: There are some CPU hotpots when processing large data when IO is highly optimized: 1. Sort : memory access to compare with 2 values can be bottleneck. 2. Aggregation : hash construction for UnorderedPartitionedKVWriter can be bottleneck. 3. Filter : memory access to compare the key values with given condition. This issue is a umbrella jira for CPU optmizations at Tez side. Related works: Alphasort: http://dl.acm.org/citation.cfm?id=615237 Multi-Core, Main-Memory Joins: Sort vs. Hash Revisited: https://cs.uwaterloo.ca/~tozsu/publications/other/p168-balkesen.pdf was: There are some CPU hotpots when processing large data when IO is highly optimized: 1. Sort : memory access to compare with 2 values can be bottleneck. 2. Aggregation : hash construction for UnorderedPartitionedKVWriter can be bottleneck. 3. Filter : memory access to compare the key values with given condition. This issue is a umbrella jira for CPU optmizations at Tez side. Related works: Alphasort: http://dl.acm.org/citation.cfm?id=615237 > [Umbrella] CPU optimizations for hotspots > ----------------------------------------- > > Key: TEZ-2605 > URL: https://issues.apache.org/jira/browse/TEZ-2605 > Project: Apache Tez > Issue Type: Improvement > Reporter: Tsuyoshi Ozawa > > There are some CPU hotpots when processing large data when IO is highly optimized: > 1. Sort : memory access to compare with 2 values can be bottleneck. > 2. Aggregation : hash construction for UnorderedPartitionedKVWriter can be bottleneck. > 3. Filter : memory access to compare the key values with given condition. > This issue is a umbrella jira for CPU optmizations at Tez side. > Related works: > Alphasort: http://dl.acm.org/citation.cfm?id=615237 > Multi-Core, Main-Memory Joins: Sort vs. Hash Revisited: https://cs.uwaterloo.ca/~tozsu/publications/other/p168-balkesen.pdf -- This message was sent by Atlassian JIRA (v6.3.4#6332)