My team has started using Docling for document parsing in Databricks. The parsing quality is impressive, but we occasionally run into GIL-related runtime failures and instability, especially when processing larger workloads. Has anyone found a reliable way to run Docling with Databricks agent or AI workloads? We'd appreciate advice on batching, scaling, deployment patterns, or alternative services that work better in this environment.
3 Answers
For a more production-friendly setup, consider running Docling as a separate serving process instead of embedding it directly in every Databricks task. That gives you a scalable endpoint, isolates parser failures, and can be more economical than repeatedly starting the full runtime.
We ran into similar problems when processing too much in a single job. Splitting the workload into smaller batches and spreading them across separate workers made the GIL failures less frequent. It still needs some monitoring, but the setup became usable.
We compared Docling with Kreuzberg, also known as xberg, on a cloud GPU platform. Kreuzberg was noticeably faster and more reliable in our tests, with better task performance. Docling is capable, but it may be worth benchmarking alternatives against your actual document mix before committing to it.

Related Questions
Neural Network Simulation Tool
xAI Grok Token Calculator
DeepSeek Token Calculator
Google Gemini Token Calculator
Meta LLaMA Token Calculator
OpenAI Token Calculator