| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The most important change of this patch
is a restructring of the database schema
in order to better support current
and future use cases.
In particular, the 'result' table has been reduced
in size (which is important since this table is
the one that will grow on a regular basis), and
a 'bmcontext' table has been introduced as an extra
structural level that is expected to make certain
queries faster than they would have otherwise been
(due to reduced need for complex join expressions
etc.).
|
|
|
|
|
|
|
|
|
| |
The 'get rankedbenchmarks' request now considers only
benchmarks matching a certain filter. E.g. specifying
'Graphics*' as the test case filter and '*' for the
test function and data tag filters, ensures that only
benchmarks with test cases beginning with "Graphics"
will be processed.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The URL used for opening a 'details' pages is now shorter and
more readable by replacing the <arg> tags with single spaces.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This patch removes the assumption that benchmark results are always
positive. Some metrics, like the 'events' metric, may produce
zero valued results. To support zero values, the ratio between
two results r1 and r2 is expressed as (r1 + 1) / (r2 + 1) instead
of just r1 / r2.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|