All sub-jobs in this test exited successfully.

This page contains the results of the spruce bandwidth test with the wgpass streaming configuration. Scroll down to see:

Summary of main results,
Details of the streaming configuration,
Links to other html pages produced by this test,
Bar charts of rate and bandwidth for each WG within each stream (HLT2 only),
A pie chart of all lines split by WGs (HLT2 and sprucing only),
Information about the input sample,
Stacked histograms of all lines, split by WG, of rate/bandwidth metrics.

Main results:

	Stream	Total Retention (%)	Rate (kHz)	Avg Total Event Size (kB)	Total Bandwidth (GB/s)	Avg DstData Size (kB)	DstData Bandwidth (GB/s)
0	charm	49.6	89.6	12.6	1.13	12.3	1.1
1	qee	43.3	78.2	6.71	0.525	6.4	0.5
2	rd	8.31	15	30.8	0.461	30.3	0.455
3	bnoc	5.63	10.2	36.7	0.373	36.3	0.368
4	trackeff	0.859	1.55	94.6	0.147	94.3	0.146
5	b2oc	1.61	2.91	48.8	0.142	48.4	0.141
6	ift	0.587	1.06	91.3	0.0968	91	0.0965
7	bandq	3.84	6.93	12.7	0.0878	12.3	0.0855
8	b2cc	0.521	0.94	79.4	0.0747	78.3	0.0736

The total bandwidth (rate) was measured to be 3.04 GB/s (206.32 kHz).

The streaming configuration (i.e. which lines went to each stream) can be found in JSON format here.
This streaming configuration is our current set of lines to be used in the next data-taking period.
"DstData" is the raw bank to which reconstructed information (candidates, other reconstructed tracks etc.) are saved.
The "DstData bandwidth" is therefore the bandwidth counting only that raw bank.
The total event size (and total bandwidth) count all raw banks (incl. DstData, and detector raw banks if present) in the file.
NB: In real data-taking, raw banks are now left uncompressed when writing, and then the whole file is compressed afterwards. We account for this compression by multiplying event sizes and bandwidths by a scaling factor to give accurate per-stream bandwidths. The scaling factor is calculated for each file in the test as: '(size of the compressed file) / (size of the uncompressed file)'.

Further results can be found in the links below:

See: RTA & DPA Workflow for reference figures regarding bandwidth.

The number of selection lines per working group:

"Other" category contains those lines with a parsed name that doesn't belong to any known WG.
To make lines properly categorized, one should follow the naming convention - name of lines should start with `Hlt2/Spruce[WG]_`.

Input sample information:

Config file: tmp/spruce_bandwidth_latest_input__turbo.yaml
Input rate: 180.51 kHz
Number of interactions per bunch crossing (ν): 7.6
Radius of VELO opening: 5.1 mm

Stacked histograms of all lines, split by WG, of rate/bandwidth metrics:
The total distributions are shown as a stacked histogram, split into several histograms of WGs.
The distributions per WG is attached in the html page linked above.
Total event size is calculated from summing all raw banks in the file (including DstData).
Where appropriate, the DstData raw bank size and DstData bandwidth are calculated from summing only the DstData raw bank.