https://techrawcull.netlify.app/tags/concurrency/Recent content in Concurrency on RawCullHugoenSat, 01 Aug 2026 15:21:25 +0200https://techrawcull.netlify.app/docs/concurrency-revised/Sat, 01 Aug 2026 00:00:00 +0000https://techrawcull.netlify.app/docs/concurrency-revised/<h1 id="concurrency">Concurrency<a class="td-heading-self-link" href="#concurrency" aria-label="Heading self-link"></a></h1> <p>This page documents concurrency in the <code>RawCullAIModels</code> branch of RawCull and in the first-party Swift packages checked out beside it. The audit covers production source in the RawCull app, <code>DecodeEncodeGeneric</code>, <code>ParseRsyncOutput</code>, <code>PhotoAIKit</code>, <code>PhotoAnalysisKit</code>, <code>RawCullCore</code>, <code>RawParserKit</code>, <code>RsyncArguments</code>, <code>RsyncProcessStreaming</code>, and <code>RsyncAnalyse</code>.</p> <p>RawCull uses concurrency to keep SwiftUI responsive while it scans folders, reads RAW metadata, extracts and caches previews, calculates sharpness, creates similarity artifacts, groups bursts, runs AI models, downloads model assets, and streams rsync output.</p>https://techrawcull.netlify.app/docs/heavy/Tue, 19 May 2026 00:00:00 +0000https://techrawcull.netlify.app/docs/heavy/<h1 id="synchronous-code">Synchronous Code<a class="td-heading-self-link" href="#synchronous-code" aria-label="Heading self-link"></a></h1> <p>Most RawCull code uses async/await, actors, and task groups. Some Apple framework work is still fundamentally synchronous: ImageIO thumbnail decode, CoreImage RAW rendering, JPEG encoding, and direct binary MakerNote parsing. This page explains where that work lives and how the app keeps it from freezing the UI or starving Swift&rsquo;s cooperative executor.</p> <h2 id="source-map">Source Map<a class="td-heading-self-link" href="#source-map" aria-label="Heading self-link"></a></h2> <table> <thead> <tr> <th>Area</th> <th>Files</th> </tr> </thead> <tbody> <tr> <td>Cancellation-aware blocking bridge</td> <td><code>RawParserKit/Sources/RawParserKit/CancellableImageIOWork.swift</code></td> </tr> <tr> <td>Thumbnail extraction</td> <td><code>SonyThumbnailExtractor.swift</code>, <code>NikonThumbnailExtractor.swift</code></td> </tr> <tr> <td>Embedded JPEG extraction</td> <td><code>JPGSonyARWExtractor.swift</code>, <code>JPGNikonNEFExtractor.swift</code>, <code>SonyRAWJPEGCreator.swift</code></td> </tr> <tr> <td>MakerNote parsing</td> <td><code>SonyMakerNoteParser.swift</code>, <code>NikonMakerNoteParser.swift</code></td> </tr> <tr> <td>App callers</td> <td><code>RequestThumbnail.swift</code>, <code>ScanAndCreateThumbnails.swift</code>, <code>ExtractAndSaveJPGs.swift</code>, <code>ScanAndExtractJPGs.swift</code>, <code>ZoomPreviewHandler.swift</code></td> </tr> <tr> <td>Sharpness scoring</td> <td><code>FocusMaskEngine+Scoring.swift</code>, <code>FocusMaskEngine+MaskGeneration.swift</code></td> </tr> </tbody> </table> <h2 id="why-blocking-work-matters">Why Blocking Work Matters<a class="td-heading-self-link" href="#why-blocking-work-matters" aria-label="Heading self-link"></a></h2> <p>Swift&rsquo;s cooperative thread pool expects async tasks to suspend instead of occupying threads for long periods. ImageIO and CoreImage calls often do not suspend; they block until decode/render work is done.</p>