From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 82050] R9270X pyrit benchmark perf regressions with latest kernel/llvm Date: Tue, 19 Aug 2014 22:22:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1553886886==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B34708921E for ; Tue, 19 Aug 2014 15:22:42 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1553886886== Content-Type: multipart/alternative; boundary="1408486962.D50e0.29259"; charset="us-ascii" --1408486962.D50e0.29259 Date: Tue, 19 Aug 2014 22:22:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=82050 --- Comment #20 from Andy Furniss --- (In reply to comment #18) > Does the pyrit benchmark include compile time when calculating PMKs/s ? The > patch you've bisected unrolls a loop that makes the pyrit kernel really big, > so it will take longer to compile. > > Is it possible to run the benchmark for longer? If so, does the gap between > good and bad shrink? It runs for 1min 16s as is, TBH I don't use/know pyrit - the only reason I have it is when I got my radeonsi and was reading how to get opencl there was a link to it as an example of a working app in the wiki. It does seem to build up speed as time progresses, but now it's slower it seems to plateau slightly longer before the end than it used to. Maybe it's just not a representative test - hence my query about glxgears, I haven't found any "real" opencl use to benchmark yet - x264 would be nice, but it seems it needs things not yet implemented. -- You are receiving this mail because: You are the assignee for the bug. --1408486962.D50e0.29259 Date: Tue, 19 Aug 2014 22:22:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 20 on bug 82050 from 
(In reply to comment #18)
> Does the pyrit benchmark include compile time when calculating PMKs/s ? The
> patch you've bisected unrolls a loop that makes the pyrit kernel really big,
> so it will take longer to compile.
> 
> Is it possible to run the benchmark for longer?  If so, does the gap between
> good and bad shrink?

It runs for 1min 16s as is, TBH I don't use/know pyrit - the only reason I have
it is when I got my radeonsi and was reading how to get opencl there was a link
to it as an example of a working app in the wiki.

It does seem to build up speed as time progresses, but now it's slower it seems
to plateau slightly longer before the end than it used to.

Maybe it's just not a representative test - hence my query about glxgears, I
haven't found any "real" opencl use to benchmark yet - x264 would be nice, but
it seems it needs things not yet implemented.

You are receiving this mail because:
  • You are the assignee for the bug.
--1408486962.D50e0.29259-- --===============1553886886== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1553886886==--