search for: fieldchang

I think it would be super useful to give LNT a RESTful interface. As LNT grows, it would be nice to be able to update some of the pages with Ajax(or json). Especially for pages with long load times, it makes sense to be able to speed up load times, by fetching the data after page load. It would also allow us to build more dynamic pages, and allow non-web clients better structured access to LNT

From: Elena Lepilkina Sent: Monday, April 25, 2016 2:33 PM To: 'James Molloy' <james at jamesmolloy.co.uk>; Kristof Beyls <Kristof.Beyls at arm.com>; Mehdi Amini <mehdi.amini at apple.com> Cc: nd <nd at arm.com>; Matthias Braun <matze at braunis.de> Subject: RE: [llvm-dev] RFC: LNT/Test-suite support for custom metrics and test parameterization Hi everyone,

...LNT/Test-suite support for custom metrics and test parameterization I am really torn about this. When I implemented the regression tracking stuff recently, it really showed me how badly we are scaling. On our production server, the run ingestion can take well over 100s. Time is mostly spent in FieldChange generation and regression grouping. Both have to access a lot of recent samples. This is not the end of the world, because it runs in a background process. Where this really sucks is when a regression has a lot indicators. The web interface renders these in a graph, and just trying to pull down 1...

...est parameterization > > > > I am really torn about this. > > > > When I implemented the regression tracking stuff recently, it really > showed me how badly we are scaling. On our production server, the run > ingestion can take well over 100s. Time is mostly spent in FieldChange > generation and regression grouping. Both have to access a lot of recent > samples. This is not the end of the world, because it runs in a background > process. Where this really sucks is when a regression has a lot > indicators. The web interface renders these in a graph, and just t...

...test parameterization > > > > I am really torn about this. > > > > When I implemented the regression tracking stuff recently, it really showed me how badly we are scaling. On our production server, the run ingestion can take well over 100s. Time is mostly spent in FieldChange generation and regression grouping. Both have to access a lot of recent samples. This is not the end of the world, because it runs in a background process. Where this really sucks is when a regression has a lot indicators. The web interface renders these in a graph, and just trying to pull down 1...

...> and test parameterization > > > > I am really torn about this. > > > > When I implemented the regression tracking stuff recently, it really showed me how badly we are scaling. On our production server, the run ingestion can take well over 100s. Time is mostly spent in FieldChange generation and regression grouping. Both have to access a lot of recent samples. This is not the end of the world, because it runs in a background process. Where this really sucks is when a regression has a lot indicators. The web interface renders these in a graph, and just trying to pull down 1...