feat: add decoding as a multi-threaded CLARA engine#1229
Open
baltzell wants to merge 44 commits into
Open
Conversation
Collaborator
Author
auto-merge was automatically disabled
May 11, 2026 22:46
Pull request was converted to draft
This reverts commit d1dce3b.
There was a problem hiding this comment.
Pull request overview
This PR introduces a multi-threaded CLARA decoder stage by adding a new DecoderEngine that decodes EVIO to HIPO using a pool of CLASDecoder instances, and updates the example CLARA service chain to use it.
Changes:
- Add
org.jlab.clas.reco.DecoderEngine(direct CLARAEngine) that decodes EVIO→HIPO using a decoder pool. - Add “sharing” constructors in
CLASDecoder/DetectorEventDecoderto reuseConstantsManagerinstances across pooled decoders. - Update
etc/services/rgd-clarode.ymlto useEvioToEvioReaderand insert the newDECOengine.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| etc/services/rgd-clarode.yml | Switches the reader and inserts the new decoder engine into the CLARA chain. |
| common-tools/clas-reco/src/main/java/org/jlab/clas/reco/DecoderEngine.java | New multi-threaded decoder engine implementation using a pooled CLASDecoder. |
| common-tools/clas-detector/src/main/java/org/jlab/detector/decode/DetectorEventDecoder.java | Adds constructors/initialization options to share constants managers for DB access. |
| common-tools/clas-detector/src/main/java/org/jlab/detector/decode/CLASDecoder.java | Adds a “share” constructor and a convenience getDecodedEvent(EvioDataEvent) overload. |
| common-tools/clara-io/src/main/java/org/jlab/io/clara/EvioToEvioReader.java | Alters reported byte order for EVIO input events. |
Comments suppressed due to low confidence (3)
common-tools/clas-reco/src/main/java/org/jlab/clas/reco/DecoderEngine.java:69
- In
configure, thetimestampoption is applied viasetVariation(...)instead ofsetTimestamp(...). This overwrites the variation with the timestamp string and the timestamp is never set on the decoder pool instances.
if (i % constantsShared == 0) {
d0 = new CLASDecoder();
if (json.has("variation")) d0.setVariation(json.getString("variation"));
if (json.has("timestamp")) d0.setVariation(json.getString("timestamp"));
d = d0;
common-tools/clas-reco/src/main/java/org/jlab/clas/reco/DecoderEngine.java:91
- The EVIO byte order is forced to LITTLE_ENDIAN when constructing
EvioDataEvent. This ignores the ByteBuffer's actual order (and differs fromReconstructionEngine, which usesbb.order()). If an input EVIO stream/file is big-endian, decoding will be incorrect. Use the buffer's order (or the reader-reported file byte order) instead of hard-coding LITTLE_ENDIAN.
if (input.getMimeType().equals("binary/data-evio")) {
EvioDataEvent evio;
try {
ByteBuffer bb = (ByteBuffer) input.getData();
//evio = new EvioDataEvent(bb.array(), bb.order());
evio = new EvioDataEvent(bb.array(), ByteOrder.LITTLE_ENDIAN);
} catch (Exception e) {
common-tools/clas-reco/src/main/java/org/jlab/clas/reco/DecoderEngine.java:103
- A decoder taken from the pool is only returned via
pool.put(d)on the success path. If decoding or event conversion throws afterpool.take(), the decoder is leaked from the pool, and repeated failures can eventually drain the pool and stall processing. Return the decoder to the pool in afinallyblock (or use a try-with-resources style helper) so it is always released.
CLASDecoder d = pool.take();
hipo = new HipoDataEvent(d.getDecodedEvent(evio),schema);
pool.put(d);
output.setData("binary/data-hipo", hipo.getHipoEvent());
} catch (Exception e) {
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

In the past year, the decoder was sped up enough to be usable as the (single-threaded) CLARA I/O service
DecoderReader. With current reconstruction speeds, that scales linearly up to about 32 threads, where it becomes I/O-bound by (single-threaded) decoding.This PR adds the decoder as a (multi-threaded) CLARA engine
DecoderEngine, based on a pool ofCLASDecoderobjects in lieu of a thread-safe decoder. Unlike other engines in COATJAVA, this implements CLARA'sEngineclass directly, rather than extendingReconstructionEngine.For database access, new "share" constructors for
CLASDecoderandDetectorEventDecoderare added to inherit a previous instance'sConstantsManagerobjects, rather than initializing new ones. All but the pool's first decoder objects use these new constructors for database sharing, akin toReconstructionEngine.Here's the rough performance for a 24-thread job on a farm25 node with
etc/services/rgd-clarode.yml. The 12 ms/event for the DECO engine suggests some thread contention, e.g., synchronizedConstantsManagercalls, since it's few-ms when run single-threaded.