search for: runid

...>> compile-time by more than 10%. > >Interesting. For some reason it also regresses huffbench quite a bit. This is because the ScopBottomUp patch file invalids the scop detection for huffbench. The run-time of huffbench with different options are shown as follows: clang: 19.1680s (see runid=14) polly without ScopBottomUp patch file: 14.8340s (see runid=16) polly with ScopBottomUp patch file: 19.2920s (see runid=21) As you can see, the ScopBottomUp patch file shows almost the same execution performance with clang. That is because no invalid scops is detected with this patch file at all...

...; >>>Interesting. For some reason it also regresses huffbench quite a bit. >> >> This is because the ScopBottomUp patch file invalids the scop detection for huffbench. The run-time of huffbench with different options are shown as follows: >> >> clang: 19.1680s (see runid=14) >> >> polly without ScopBottomUp patch file: 14.8340s (see runid=16) >> >> polly with ScopBottomUp patch file: 19.2920s (see runid=21) >> >> As you can see, the ScopBottomUp patch file shows almost the same execution performance with clang. That is because no...

...re than 10%. >> >>Interesting. For some reason it also regresses huffbench quite a bit. > > This is because the ScopBottomUp patch file invalids the scop detection for huffbench. The run-time of huffbench with different options are shown as follows: > > clang: 19.1680s (see runid=14) > > polly without ScopBottomUp patch file: 14.8340s (see runid=16) > > polly with ScopBottomUp patch file: 19.2920s (see runid=21) > > As you can see, the ScopBottomUp patch file shows almost the same execution performance with clang. That is because no invalid scops is detect...

On 07/30/2013 10:03 AM, Star Tan wrote: > Hi Tobias and all Polly developers, > > I have re-evaluated the Polly compile-time performance using newest > LLVM/Polly source code. You can view the results on > http://188.40.87.11:8000 > <http://188.40.87.11:8000/db_default/v4/nts/16?compare_to=9&baseline=9&aggregation_fn=median>. > > Especially, I also evaluated

Hi Tobias and all Polly developers, I have re-evaluated the Polly compile-time performance using newest LLVM/Polly source code. You can view the results on http://188.40.87.11:8000. Especially, I also evaluated our r187102 patch file that avoids expensive failure string operations in normal execution. Specifically, I evaluated two cases for it: Polly-NoCodeGen: clang -O3 -load

..., myRoot ) @myScript = aScript @myId = @myScript.id @myName = File.basename(@myScript.name, "*.rb") @usecase = @myName @myRun = aRun @myRoot = myRoot @rootDir = "#{RAILS_ROOT}" @launch = aRun.launched @runenv = runenv @myURI = myURI @runid = aRun.id @optionStrg = aRun.options @myBrowser = '''' @myHwnd = 0 end end **********a sample child script class (Just the run method. bunch of other methods in full script) class SearchTest < ScriptMain def run( limit = 5.minutes ) begin puts '...

...-enable-my-new-pass'. To stick with the LNT concepts, tests enabling new passes are stored as a different "machine". The only way I know to be able to do a comparison between runs on 2 different "machine"s is to manually edit the URL for run vs run comparison and fill in the runids of the 2 runs you want to compare. For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf<http://llvm.org/perf> server: http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 I had to manually look up...

...t have this problem initially and when the system is well tuned and set up it works just fine example : performance numbers I promised : Following table illustrates the performance between ext2/ext3/ocfs/raw with AIO. FS Type tpmC (TPS*) Total CPU % (User / Sys) BInput (Mb/s) BOutput (Mb/s) Runid ext2-aio 2039 (130) 35.59 ( 24.59 / 11.00 ) 11.5 1.82 2142 ext3-aio (ordered) 2243 (129) 34.3 ( 22.06 / 12.25 ) 11.7 1.9 2162 ext3-aio (journal) 2380 (130) 37.44 ( 25.28 / 12.16 ) 12.2 3.1 2156 raw-aio 10742 (349) 63.97 ( 47.44 / 16.53 ) 7.3 5.4 2191 ocfs-aio 10756 (352) 65.28 ( 47.84 / 17.44 ) 7.2...

...t have this problem initially and when the system is well tuned and set up it works just fine example : performance numbers I promised : Following table illustrates the performance between ext2/ext3/ocfs/raw with AIO. FS Type tpmC (TPS*) Total CPU % (User / Sys) BInput (Mb/s) BOutput (Mb/s) Runid ext2-aio 2039 (130) 35.59 ( 24.59 / 11.00 ) 11.5 1.82 2142 ext3-aio (ordered) 2243 (129) 34.3 ( 22.06 / 12.25 ) 11.7 1.9 2162 ext3-aio (journal) 2380 (130) 37.44 ( 25.28 / 12.16 ) 12.2 3.1 2156 raw-aio 10742 (349) 63.97 ( 47.44 / 16.53 ) 7.3 5.4 2191 ocfs-aio 10756 (352) 65.28 ( 47.84 / 17.44 ) 7.2...

...-enable-my-new-pass'. To stick with the LNT concepts, tests enabling new passes are stored as a different "machine". The only way I know to be able to do a comparison between runs on 2 different "machine"s is to manually edit the URL for run vs run comparison and fill in the runids of the 2 runs you want to compare. For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf<http://llvm.org/perf> server: http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 I had to manually look up...

...-enable-my-new-pass'. To stick with the LNT concepts, tests enabling new passes are stored as a different "machine". The only way I know to be able to do a comparison between runs on 2 different "machine"s is to manually edit the URL for run vs run comparison and fill in the runids of the 2 runs you want to compare. For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf<http://llvm.org/perf> server: http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 I had to manually look up...

On 21 Apr 2016, at 15:00, Elena Lepilkina <Elena.Lepilkina at synopsys.com<mailto:Elena.Lepilkina at synopsys.com>> wrote: Hi Kristof and Daniel, Thanks for your answers. Unfortunately I haven’t tried scaling up to a large data set before. Today I tried and results are quite bad. So database scheme should be rebuild. Now I thought about creating one sample table for each test-suite,

...-enable-my-new-pass'. To stick with the LNT concepts, tests enabling new passes are stored as a different "machine". The only way I know to be able to do a comparison between runs on 2 different "machine"s is to manually edit the URL for run vs run comparison and fill in the runids of the 2 runs you want to compare. For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf<http://llvm.org/perf> server: http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 I had to manually look up...

...tick with the LNT concepts, tests enabling new passes are stored as a > different "machine". > > The only way I know to be able to do a comparison between runs on 2 > different "machine"s is to manually edit the URL for run vs run comparison > > and fill in the runids of the 2 runs you want to compare. > > For example, the following URL is a comparison of > green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public > llvm.org/perf server: > > http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 > > I had to manu...

...with the LNT concepts, tests enabling new passes are stored as a different "machine". > > The only way I know to be able to do a comparison between runs on 2 > different "machine"s is to manually edit the URL for run vs run > comparison > > and fill in the runids of the 2 runs you want to compare. > > For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf server: > > http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 > > I had to manually lo...

...tick with the LNT concepts, tests enabling new passes are stored as a different "machine". > > The only way I know to be able to do a comparison between runs on 2 > different "machine"s is to manually edit the URL for run vs run > comparison > > and fill in the runids of the 2 runs you want to compare. > > For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf<http://llvm.org/perf> server: > > http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 >...