search for: runids

At 2013-07-31 22:50:57,"Tobias Grosser" <tobias at grosser.es> wrote: >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 >>

At 2013-08-01 23:29:14,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/31/2013 09:23 PM, Star Tan wrote: >> At 2013-07-31 22:50:57,"Tobias Grosser" <tobias at grosser.es >> <mailto:tobias at grosser.es>> wrote: >> >>>On 07/30/2013 10:03 AM, Star Tan wrote: >>>> Hi Tobias and all Polly developers,

On 07/31/2013 09:23 PM, Star Tan wrote: > At 2013-07-31 22:50:57,"Tobias Grosser" <tobias at grosser.es > <mailto:tobias at grosser.es>> wrote: > >>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

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

The following code works fine as long as I don''t try to run it through the distributed server. It doesn''t get there... It runs fine out of delayed_job, runs fine if called directly. But if ''distrib'' is true (the default) it runs right up to the call to the server and right past it without getting to the server or raising any errors. Am using Ruby 1.8.6.26 ,

...-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...

Wim, Thanks for your prompt response on this. The tpmC figures look very impressive, and tpmC is read intensive. I had already read note 236679.1 "Comparing Performance Between RAW IO vs OCFS vs EXT2/3" which I guess is the article to which you are referring; it made me suspect that the poor performance was due to the lack of an OS IO cache but I wasn't sure. The database is

Wim, Thanks for your prompt response on this. The tpmC figures look very impressive, and tpmC is read intensive. I had already read note 236679.1 "Comparing Performance Between RAW IO vs OCFS vs EXT2/3" which I guess is the article to which you are referring; it made me suspect that the poor performance was due to the lack of an OS IO cache but I wasn't sure. The database is

...-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 manua...

...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 loo...

...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 > &...