heffner Posted February 7, 2020 Report Share Posted February 7, 2020 Performing large OCR batches or other long-running background tasks using Connect currently feels like "go for it and hopefully everything will work as expected" 😉 ... most of the time, it's exactly what happens, but sometimes it's not and here some improvements could help to make it less magic... Pause and/or Stop background tasks already "in progress" Adjust priority of background tasks, to let single OCR jobs run while having a large batch in parallel Integrate batch results like "Feature -> OCRed" after a configurable item count, e.g. after 1.000 or 10k items Run OCR background tasks on a(ll) Node(s) instead of the main Connect server Stephan Quote Link to comment Share on other sites More sharing options...
ŁukaszBachman Posted February 10, 2020 Report Share Posted February 10, 2020 Hello Stephan, This all sounds like good ideas to me, I'll include them in our roadmap for the future. We have some long-term plans for improvements in overall experience of using tasks in Connect, where I would like to address these as well. Leveraging Nodes for background tasks is also something that we are planning to do, but that one will be the hardest to do. Thank you for sharing your thoughts and feedback. P.S. Current version allows for stopping (removing) tasks which are running, but this depends on the type of the task (not all of them support this feature). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.