-
Notifications
You must be signed in to change notification settings - Fork 6
/
defs.tex
53 lines (38 loc) · 2.41 KB
/
defs.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
\chapter*{Definitions}
{\flushleft \textbf{\DataGen:}} The data generator provided by the
\ldbcfinbench, which is responsible for generating the data needed to run the
benchmark.
{\flushleft \textbf{DBMS:}} A DataBase Management System.
{\flushleft \textbf{\ldbcfinbench:}} Linked Data Benchmark Council Financial
Benchmark.
{\flushleft \textbf{Query Mix:}} Refers to the ratio between read and update
queries of a workload, and the frequency at which they are issued.
{\flushleft \textbf{SF (Scale Factor):}} The \ldbcfinbench is designed to target
systems of different sizes and scales. The scale factor determines the size of the
data used to run the benchmark, measured in Gigabytes.
{\flushleft \textbf{SUT:}} The System Under Test is defined to be the database
system where the benchmark is executed.
{\flushleft \textbf{Test Driver:}} A program provided by the \ldbcfinbench,
which is responsible for executing the different workloads and gathering the
results.
{\flushleft \textbf{Full Disclosure Report (FDR):}} The FDR is a document that
allows the reproduction of any benchmark result by a third-party. This contains
a complete description of the SUT and the circumstances of the benchmark run, \eg
the configuration of SUT, dataset and test driver, \etc
{\flushleft \textbf{Test Sponsor:}} The Test Sponsor is the company officially
submitting the Result with the FDR and will be charged the filing fee. Although
multiple companies may sponsor a Result together, for the purposes of the LDBC
processes the Test Sponsor must be a single company. A Test Sponsor need not be
a LDBC member. The Test Sponsor is responsible for maintaining the FDR with any
necessary updates or corrections. The Test Sponsor is also the name used to
identify the Result.
%{\flushleft \textbf{Test Run:}} The entire period of time during which Drivers
%submit and the SUT completes Transactions other than Trade-Cleanup.
%
%{\flushleft \textbf{Transaction:}} A Database Transaction is an ACID unit of work.
%{\flushleft \textbf{Valid Transaction:}} The term Valid Transaction refers to
%any Transaction for which input data has been sent in full by the Driver, whose
%processing has been successfully completed on the SUT and whose correct output
%data has been received in full by the Driver.
{\flushleft \textbf{Workload:}} A workload refers to a set of queries of a given nature
(\ie interactive, analytical, business), how they are issued and at which rate.