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
+16-1Lines changed: 16 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -259,7 +259,6 @@ aid benchmark error
259
259
1 syn-1.0.89 Failed to compile...
260
260
```
261
261
262
-
263
262
## New benchmarking design
264
263
We are currently implementing a new design for dispatching benchmarks to collector(s) and storing
265
264
them in the database. It will support new use-cases, like backfilling of new benchmarks into a parent
@@ -296,3 +295,19 @@ Columns:
296
295
*`completed`: Completed request.
297
296
***backends** (`text NOT NULL`): Comma-separated list of codegen backends to benchmark. If empty, the default set of codegen backends will be benchmarked.
298
297
***profiles** (`text NOT NULL`): Comma-separated list of profiles to benchmark. If empty, the default set of profiles will be benchmarked.
298
+
||||||| parent of cca4e3d5 (Feat; job_queue table definition & mark a request as complete if all jobs are finished)
299
+
300
+
### job_queue
301
+
302
+
This table stores ephemeral benchmark jobs, which specifically tell the
303
+
collector which benchmarks it should execute. The jobs will be kept in the
304
+
table for ~30 days after being completed, so that we can quickly figure out
305
+
what master parent jobs we need to backfill when handling try builds.
306
+
307
+
```
308
+
psql# SELECT * FROM job_queue limit 1;
309
+
310
+
id request_id target backend benchmark_set collector_id created_at started_at completed_at status retry error
0 commit comments