You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "patrick white (JIRA)" <ji...@apache.org> on 2014/05/14 20:19:15 UTC
[jira] [Commented] (HADOOP-10554) Performance: Scan metrics for 2.4
are down compared to 0.23.9
[ https://issues.apache.org/jira/browse/HADOOP-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997846#comment-13997846 ]
patrick white commented on HADOOP-10554:
----------------------------------------
Test results update to Description:
Issue does reproduce on a small (10 node) cluster, with consistent performance difference across release lines. Numbers from the 10 node cluster actually show a larger delta than the 350 node cluster's results (>10% regression), between 2.4.0 and 0.23.9, both in runtimes and throughput.
> Performance: Scan metrics for 2.4 are down compared to 0.23.9
> -------------------------------------------------------------
>
> Key: HADOOP-10554
> URL: https://issues.apache.org/jira/browse/HADOOP-10554
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: patrick white
>
> Performance comparison benchmarks for Scan test's runtime and throughput metrics are slightly out of 5% tolerance in 2.x compared against 0.23. The trend is consistent across later releases in both lines, latest release numbers are;
> Runtime:
> 2.4.0.0 -> 73.6 seconds (avg 5 passes)
> 0.23.9.12 -> 69.4 seconds (avg 5 passes)
> Diff: -5.7%
> Throughput:
> 2.4.0.0 -> 28.67 GB/s (avg 5 passes)
> 0.23.9.12 -> 30.41 GB/s (avg 5 passes)
> Diff: -6.1%
> Scan test is specifically measuring the average map's input read performance. The diff is consistent when run on a larger (350 node) perf environment, we are in process of seeing if this reproduces in a smaller cluster, using appropriately scaled inputs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)