REVIEW 1 cited by
Fast Entropy Coding for ALICE Run 3
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
In LHC Run 3, the upgraded ALICE detector will record Pb-Pb collisions at a rate of 50 kHz usingcontinuous readout. The resulting stream of raw data at 3.5 TB/s has to be processed with a setof lossy and lossless compression and data reduction techniques to a storage data rate of 90 GB/swhile preserving relevant data for physics analysis. This contribution presents a custom losslessdata compression scheme based on entropy coding as the final component in the data reductionchain which has to compress the data rate from 300 GB/s to 90 GB/s. A flexible, multi-processarchitecture for the data compression scheme is proposed that seamlessly interfaces with the datareduction algorithms of earlier stages and allows to use parallel processing in order to keep therequired firm real-time guarantees of the system. The data processed inside the compressionprocess have a structure that allows the use of an rANS entropy coder with more resource efficientstatic distribution tables. Extensions to the rANS entropy coder are introduced to efficientlywork with these static distribution tables and large but sparse source alphabets consisting of upto 25 Bit per symbol. Preliminary performance results show compliance with the firm real-timerequirements while offering close-to-optimal data compression.
Forward citations
Cited by 1 Pith paper
-
Efficient high performance computing with the ALICE Event Processing Nodes GPU-based farm
ALICE's 2800-GPU Event Processing Nodes farm sustains 50 kHz lead-lead collision processing with a power usage effectiveness of 1.05 using adiabatic cooling.
Discussion (0). Continue with ORCID to comment.