similar to: [LLVMdev] [patches] Two smaller LNT fixes

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] [patches] Two smaller LNT fixes"

2010 Dec 07
1
[LLVMdev] LNT somewhere hosted and used?
On 12/06/2010 03:33 PM, Bob Wilson wrote: > > On Dec 6, 2010, at 10:40 AM, Tobias Grosser wrote: > >> Hi, >> >> I have been following the development of the /zorg/trunk/lnt project for >> a while and am wondering if there is some regular LLVM performance >> testing using LNT that can be accessed online? Are there any plans to >> create an officially
2010 Dec 06
2
[LLVMdev] LNT somewhere hosted and used?
Hi, I have been following the development of the /zorg/trunk/lnt project for a while and am wondering if there is some regular LLVM performance testing using LNT that can be accessed online? Are there any plans to create an officially used web service for this like e.g the llvm buildbots? Thanks a lot Tobi
2013 Jun 27
0
[LLVMdev] [LNT] Question about results reliability in LNT infrustructure
Just forwarding this to the list, my original reply was bounced. On Jun 27, 2013, at 11:14 AM, Chris Matthews <chris.matthews at apple.com> wrote: > There are a few things we have looked at with LNT runs, so I will share the insights we have had so far. A lot of the problems we have are artificially created by our test protocols instead of the compiler changes themselves. I have been
2013 Jun 27
0
[LLVMdev] [LNT] Question about results reliability in LNT infrustructure
On 06/23/2013 11:12 PM, Star Tan wrote: > Hi all, > > > When we compare two testings, each of which is run with three samples, how would LNT show whether the comparison is reliable or not? > > > I have seen that the function get_value_status in reporting/analysis.py uses a very simple algorithm to infer data status. For example, if abs(self.delta) <= (self.stddev *
2010 Dec 06
0
[LLVMdev] LNT somewhere hosted and used?
On Dec 6, 2010, at 10:40 AM, Tobias Grosser wrote: > Hi, > > I have been following the development of the /zorg/trunk/lnt project for > a while and am wondering if there is some regular LLVM performance > testing using LNT that can be accessed online? Are there any plans to > create an officially used web service for this like e.g the llvm buildbots? I have a nightly tester
2017 Jun 27
5
LNT Server offline
Hi, So, I owe you all an apology. I was totally unaware that the llvm.org server, running at UIUC, was still in operation and hosting an active LNT instance. I was under the assumption the LNT server ran elsewhere. As a result, the ability for the LNT bots to submit run information to the "old" LNT server is now gone. I am very sorry for this oversight. In speaking with Chris
2015 Mar 19
2
[LLVMdev] LNT Error 500
Hi Renato, on our public LNT servers I see again error 500 messages every once in a while: http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly-fast Could you possibly have a look? Tobias
2013 Jun 27
7
[LLVMdev] [LNT] Question about results reliability in LNT infrustructure
There are a few things we have looked at with LNT runs, so I will share the insights we have had so far. A lot of the problems we have are artificially created by our test protocols instead of the compiler changes themselves. I have been doing a lot of large sample runs of single benchmarks to characterize them better. Some key points: 1) Some benchmarks are bi-modal or multi-modal, single
2013 Jun 24
5
[LLVMdev] [LNT] Question about results reliability in LNT infrustructure
Hi all, When we compare two testings, each of which is run with three samples, how would LNT show whether the comparison is reliable or not? I have seen that the function get_value_status in reporting/analysis.py uses a very simple algorithm to infer data status. For example, if abs(self.delta) <= (self.stddev * confidence_interval), then the data status is set as UNCHANGED. However, it
2013 Jun 27
2
[LLVMdev] [LNT] Question about results reliability in LNT infrustructure
On 27 June 2013 17:05, Tobias Grosser <tobias at grosser.es> wrote: > We are looking for a good way/value to show the reliability of individual > results in the UI. Do you have some experience, what a good measure of the > reliability of test results is? > Hi Tobi, I had a look at this a while ago, but never got around to actually work on it. My idea was to never use
2017 Jul 31
1
[LNT] new server instance http://lnt.llvm.org seems unstable
The run page problem were triggered by one of my commits (sorry) and should be mitigated now, see the thread at http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html <http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html> I don't know about the submission problems, could they just an occasional network problem or are they a common phenomenon? Chris did some
2012 Jun 20
0
[LLVMdev] buildbot with -vectorize
On 06/20/2012 11:07 PM, Hal Finkel wrote: > On Tue, 12 Jun 2012 11:15:12 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 02/05/2012 02:42 PM, Hal Finkel wrote: >>> I think that it would be a good idea to have a buildbot set up to >>> run the test suite with -vectorize. Could one of the existing >>> machines do this also? >>
2012 Jun 20
2
[LLVMdev] buildbot with -vectorize
On Tue, 12 Jun 2012 11:15:12 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 02/05/2012 02:42 PM, Hal Finkel wrote: > > I think that it would be a good idea to have a buildbot set up to > > run the test suite with -vectorize. Could one of the existing > > machines do this also? > > It took some time, but we have this now: > >
2012 Jun 21
2
[LLVMdev] buildbot with -vectorize
On Thu, 21 Jun 2012 01:03:46 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/20/2012 11:07 PM, Hal Finkel wrote: > > On Tue, 12 Jun 2012 11:15:12 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 02/05/2012 02:42 PM, Hal Finkel wrote: > >>> I think that it would be a good idea to have a buildbot set up to >
2012 Jun 28
2
[LLVMdev] buildbot with -vectorize
On Sun, 24 Jun 2012 14:44:45 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/24/2012 02:42 PM, Hal Finkel wrote: > > On Sun, 24 Jun 2012 08:17:32 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 06/24/2012 05:42 AM, Hal Finkel wrote: > >>> On Thu, 21 Jun 2012 16:25:13 +0200 > >>> Tobias
2012 Jun 21
0
[LLVMdev] buildbot with -vectorize
On 06/21/2012 04:23 PM, Hal Finkel wrote: > On Thu, 21 Jun 2012 01:03:46 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 06/20/2012 11:07 PM, Hal Finkel wrote: >>> On Tue, 12 Jun 2012 11:15:12 +0200 >>> Tobias Grosser<tobias at grosser.es> wrote: >>> >>>> On 02/05/2012 02:42 PM, Hal Finkel wrote: >>>>>
2012 Jun 24
0
[LLVMdev] buildbot with -vectorize
On 06/24/2012 05:42 AM, Hal Finkel wrote: > On Thu, 21 Jun 2012 16:25:13 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 06/21/2012 04:23 PM, Hal Finkel wrote: >>> On Thu, 21 Jun 2012 01:03:46 +0200 >>> Tobias Grosser<tobias at grosser.es> wrote: >>> >>>> On 06/20/2012 11:07 PM, Hal Finkel wrote: >>>>>
2014 Nov 25
2
[LLVMdev] LNT server is down
I don’t have access to that server. I have been using a cloud LNT instance for the performance runs on the green-dragon cluster. So far it has provided 100% uptime! http://llvm-lnt.herokuapp.com <http://llvm-lnt.herokuapp.com/> > On Nov 24, 2014, at 3:24 PM, Tobias Grosser <tobias at grosser.es> wrote: > > On 24.11.2014 23:54, Galina Kistanova wrote: >> Hello
2012 Jan 25
1
[LLVMdev] Settin up a LNT nightly tester to report to http://llvm.org/perf
Hi, I got a new machine on which I want to run nightly tests that track clang performance changes over the next years. I plan to use the same or a similar setup as Bob is running for his i386 tester, but for x64. (I plan to extend this, but I want to start small). To set this up I think i need two things: 1. A script to automate the separate steps A script that checks out the different svn
2017 Aug 02
2
[LNT] new server instance http://lnt.llvm.org seems unstable
> On Aug 2, 2017, at 12:43 PM, Tobias Grosser <tobias.grosser at inf.ethz.ch> wrote: > > On Tue, Aug 1, 2017, at 00:33, Matthias Braun via llvm-dev wrote: >> The run page problem were triggered by one of my commits (sorry) and >> should be mitigated now, see the thread at >> http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html >>