Color code: (critical, news during the meeting: green, news from this week: blue, news from last week: purple, no news: black)
High priority framework topics:
- Problem at end of run with lots of error messages and breaks many calibration runs https://alice.its.cern.ch/jira/browse/O2-3315
- Unfortunately, online there are still errors after fixing those that are seen in the FST (e.g. partition 2e5XVwXYwvX).
- Fix START-STOP-START for good
- Multi-threaded pipeline still not working in FST / sync processing, but only in standalone benchmark.
- Problem with QC topologies with expendable tasks- For items to do see: https://alice.its.cern.ch/jira/browse/QC-953
- First PR merged, but more to come-
- Improve DPL CPU usage (as time fraction) reporting: https://alice.its.cern.ch/jira/browse/OMON-666 has been implemented
- Investigated problem with high CPU load of idling processes, fixed 3 causes:
- DPL metric processing.
- DPL spinning at beginning of run before receiving first message.
- DPL spinning on channels that are backpressured, this one was the one that cause the high load during async 1NUMA workflow.
- Problem in QC where we collect messages in memory while the run is stopped: https://alice.its.cern.ch/jira/browse/O2-3691
Other framework tickets:
- TOF problem with receiving condition in tof-compressor: https://alice.its.cern.ch/jira/browse/O2-3681 - Saw some work, is it fixed?
- Grafana metrics: Might want to introduce additional rate metrics that subtract the header overhead to have the pure payload: low priority.
- Backpressure reporting when there is only 1 input channel: no progress.
- Stop entire workflow if one process segfaults / exits unexpectedly. Tested again in January, still not working despite some fixes. https://alice.its.cern.ch/jira/browse/O2-2710
- https://alice.its.cern.ch/jira/browse/O2-1900 : FIX in PR, but has side effects which must also be fixed.
- https://alice.its.cern.ch/jira/browse/O2-2213 : Cannot override debug severity for tpc-tracker
- https://alice.its.cern.ch/jira/browse/O2-2209 : Improve DebugGUI information
- https://alice.its.cern.ch/jira/browse/O2-2140 : Better error message (or a message at all) when input missing
- https://alice.its.cern.ch/jira/browse/O2-2361 : Problem with 2 devices of the same name
- https://alice.its.cern.ch/jira/browse/O2-2300 : Usage of valgrind in external terminal: The testcase is currently causing a segfault, which is an unrelated problem and must be fixed first. Reproduced and investigated by Giulio.
- DPL Raw Sequencer segfaults when an HBF is missing. Fixed by changing way raw-reader sends the parts, but Matthias will add a check to prevent such failures in the future. Fixed - and in addition special handling added for data with incorrect padding: will perform a forward page scan to find all sequences. This slows down the processing, but avoids crash / incorrect decoding. An alarm is printed on the infologger that data has pad padding and that thus the processing is slow.
- Found a reproducible crash (while fixing the memory leak) in the TOF compressed-decoder at workflow termination, if the wrong topology is running. Not critical, since it is only at the termination, and the fix of the topology avoids it in any case. But we should still understand and fix the crash itself. A reproducer is available.
- Support in DPL GUI to send individual START and STOP commands.
- Problem I mentioned last time with non-critical QC tasks and DPL CCDB fetcher is real. Will need some extra work to solve it. Otherwise non-critical QC tasks will stall the DPL chain when they fail.
Global calibration topics:
- TPC calib problem: Need to repeat the test with latest fixed, but as we still have problems in all online runs, I think it will require more work..
- Switched TPC IDC FLP2EPN sending for 32 orbits, should be the last change on the software side.
- Disabled per-TF logging of calib tasks, since it creates way too large log files (Up to 100 GB per run per calib node).
- TPC had problems with FLP processing stuck in IDC workflow, under investigation, but not really reproducible.
- Even with latest changes, difficult to ensure guaranteed calibration finalization at end of global run (as discussed with Ruben yesterday).
- After discussion with Peter, Giulio this morning: We should push for 2 additional states in the state machine at the end of run between RUNNING and READY:
- DRAIN: For all but O2, the transision RUNNING --> FINALIZE is identical to what we do in STOP: RUNNING --> READY at the moment. I.e. no more data will come in then.
- O2 could finalize the current TF processing with some time out, where it stops processing incoming data, and at EndOfStream trigger the calibration postprocessing.
- FINALIZE: No more data is guaranteed to come in, but the calibration could still be running. So we leave FMQ channels open, and have a time out to finalize the calibration. If input proxies have not yet received the EndOfStream, they will inject it to trigger the final calibration.
- This would require changes in O2, DD, ECS, FMQ, but all changes except for in O2 should be trivial, since all other components would not do anything in these states.
Async reconstruction
- Remaining oscilation problem: GPUs get sometimes stalled for a long time up to 2 minutes.
- Checking 2 things: does the situation get better without GPU monitoring?
- We can use increased GPU processes priority as a mitigation, but doesn't fully fix the issue.
- Improvements / performance impacts from oscilations in 1NUMA workflow:
- Rate smoothing mitigates the problem, and improves overall throughput by 3.4%.
- 1NUMA workflow with TF throttling and smoothing now reaches 82% CPU load (Due to HyperThreading, 50% CPU load is 80% of the capacity, so with 82% load we are at 92% of the max compute capacity, and 1.9s per TF.
- For comparison, 1NUMA workflow with manually tuned publishing rate, but without rate throttling, reaches 95% CPU load, and 1.75s per TF, so 8.5% faster still.
- Should still try to undertstand and improve this.
- Updated async reco performance benchmarks after CPU load fix:
- 8-core CPU workflow: 4.81s per TF (cannot run, since runs OOM very quickly)
- 16-core CPU workflow: 4.27s per TF (stable)
- 1GPU workflow: 1.83s (unstable, can run OOM, will get better with shorter TFs)
- 1NUMA workflow: 1.75s (stable)
EPN major topics:
- Switched CTF size to 10 GB - Async reco will use direct streaming from alien instead of copying to local files.
- SSD should survive this during Run 3, afterwards we might need to replace them.
- Deploying the RAMDISK cache is thus no longer needed.
- Fast movement of nodes between async / online without EPN expert intervention.
- Interface to change SHM memory sizes when no run is ongoing. Otherwise we cannot tune the workflow for both Pb-Pb and pp: https://alice.its.cern.ch/jira/browse/EPN-250
- Improve DataDistribution file replay performance, currently cannot do faster than 0.8 Hz, cannot test MI100 EPN in Pb-Pb at nominal rate, and cannot test pp workflow for 100 EPNs in FST since DD injects TFs too slowly. https://alice.its.cern.ch/jira/browse/EPN-244 NO ETA
- Need DDS/ODC feature to deploy different topologies on EPNs with MI50 and with MI100. ETA End of March + ~2 weeks - Status?
- Go to error state if a critical task (e.g. calib task) fails (taking nmin into accound). But currently we do not see failing calibration tasks at all, except for a message in infologger. ODC should go to error, and then ECS should stop the run automatically. Also when n < nmin. ETA End of March - Status?
- Lubos to provide interface to querry current EPN SHM settings - Status?
- DataDistribution and ODC InfoLogger messages not shown at shifter console since they were at level trace. Discused with Sylvain, and implemented the same severity --> level translation as in O2. Merged in both repositories. DD already updated, ODC with next software update.
Other EPN topics:
EPN farm upgrade:
- Repeated the test with repeated DMA transfer for the second test case, fails in the very same way.
- Problem disappears when amdgpu-function-calls are disabled, but this comes with a performance penalty.
- New AMD ROCm version 5.5 available:
- DMA problem with MI100 and function calls enabled doesn't appear any more. Not clear if fixed or just disappeared by chance.
- All other combinations, MI50, and MI100 without function calls do not work. Either crash or get stuck. AMD is invesigation and has a reproducer.
- AMD has requested if we can provide a standalone reproducer for this. Cheking... but current standalone event dump is broken.
TPC Raw decoding checks:
- TPC raw decoding yields incorrect results when first TfOrbit is wrong (was reported by TfBuilder, but not spotted by shift crew since messages were trace level, which is fixed already).
- Adding additional check in TPC raw decoding for sane first Orbits.
- Will also add a check on DPL level, to make sure firstOrbit received from all detectors is identical, when creating the TimeFrame first orbit.
- Since we had repeatedly situations where we have corrupt TPC raw data online but cannot reproduce, and DataDistribution provides no possibility to dump TFs after processing (currently we dump 1 permille, so chance to dump the corrupt TF is pretty low), will implement TPC TF dump in the TPC reconstruction, so we get that data (similarly to what ITS does).
Full system test issues:
Topology generation:
- Ole is investigating to use set -u or set -e to catch more errors, but has some drawbacks. Current plan is to use -u, but not -e. To be merged when Ole is back from vacation in 2 weeks. Merged
- Should test to deploy topology with DPL driver, to have the remote GUI available.
Software deployment at P2.
- O2PDPSuite updated with EMCAL fix cherry-picked yesterday, next software release will have to wait for a slot from LHC.
- Have new Pb-Pb dataset for SYNTHETIC runs. More realistic TPC data sizes but still not fully realistic. Now simulating pp and then will deploy at P2.
- Afterwards should check number of clusters and digits in more detail with more statistics, and discuss with TPC experts.
- Found several bugs in some digitizers, which broke with longer simulation window. All fixed by Sandro.
QC / Monitoring / InfoLogger updates:
- TPC has opened first PR for monitoring of cluster rejection in QC. Trending for TPC CTFs is work in progress. Ole will join from our side, and plan is to extend this to all detectors, and to include also trending for raw data sizes.
CCDB topics.
AliECS related topics:
- ECS should replace newlines in extra env field by spaces, but doesn't. Filed a bug report in JIRA - Still not done
- In preparation for supporting configurable SHM sizes, added SHM size options to ECS EPN workflow configuration. Will be passed to topology generation. Then to be checked against actual EPN SHM size settings. - DONE
GPU ROCm / compiler topics:
- Found new HIP internal compiler error when compiling without optimization: -O0 make the compilation fail with unsupported LLVM intrinsic. Reported to AMD.
- Found a new miscompilation with -ffast-math enabled in looper folllowing, for now disabled -ffast-math.
- Must create new minimal reproducer for compile error when we enable LOG(...) functionality in the HIP code. Check whether this is a bug in our code or in ROCm. Lubos will work on this.
- Found another compiler problem with template treatment found by Ruben. Have a workaround for now. Need to create a minimal reproducer and file a bug report.
- Debugging the calibration, debug output triggered another internal compiler error in HIP compiler. No problem for now since it happened only with temporary debug code. But should still report it to AMD to fix it.
TPC GPU Processing
- Random GPU crashes under investigation.
- Sergey provided fix for inverse transformation map, but not yet merged in O2. Rebased to O2/dev and fixed some issues. Will hopefully be able to check today.
- Bug in TPC QC with MC embedding, TPC QC does not respect sourceID of MC labels, so confuses tracks of signal and of background events.
- Bug in TPC Clusterizer in multi-threaded CPU DLBZS decoding, Fixed by Felix.
- 2 Minor bugs in TPC clusterization fixed.
- Added support for shifting TPC clusters in time (requested by Ruben)
- But in TPC processing with distortion correction with scaling - under investigation. But first need to validate and merge Sergey's fix for the inverse corretion, since otherwise that gives false errors in my checks.
ANS Encoding
- PR open and Matthias was working on it, not sure what is the status.
Issues currently lacking manpower, waiting for a volunteer:
- For debugging, it would be convenient to have a proper tool that (using FairMQ debug mode) can list all messages currently in the SHM segments, similarly to what I had hacked together for https://alice.its.cern.ch/jira/browse/O2-2108
- Redo / Improve the parameter range scan for tuning GPU parameters. In particular, on the AMD GPUs, since they seem to be affected much more by memory sizes, we have to use test time frames of the correct size, and we have to separate training and test data sets.