You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: database/schema.md
+56-2Lines changed: 56 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,48 @@
2
2
3
3
Below is an explanation of the current database schema. This schema is duplicated across the (currently) two database backends we support: sqlite and postgres.
4
4
5
+
6
+
## Overview
7
+
8
+
In general, the database is used to track three groups of things:
9
+
* Performance run statistics (e.g., instruction count) on a per benchmark, profile, and cache-state basis.
10
+
* Self profile data gathered with `-Zself-profile`.
11
+
* State when running GitHub bots and the performance runs (e.g., how long it took for a performance suite to run, errors encountered a long the way, etc.)
12
+
13
+
Below are some diagrams showing the basic layout of the database schema for these three uses:
A description of a rustc compiler artifact being benchmarked.
23
65
24
66
This description includes:
25
-
* name: usually a commit sha or a tag like "1.51.0"
67
+
* name: usually a commit sha or a tag like "1.51.0" but is free-form text so can be anything.
26
68
* date: the date associated with this compiler artifact (usually only when the name is a commit)
27
69
* type: currently one of "master" (i.e., we're testing a merge commit), "try" (someone is testing a PR), and "release" (usually a release candidate - though local compilers also get labeled like this).
0 commit comments