Blade bridge Analyzer out of memory issue

Vasu_Kumar_T — Wed, 09 Apr 2025 16:00:23 GMT

We are running bladebridge analyzer, and we are getting to run out of memory

we tried to increase the RAM and still it gives the same error.

We cannot run the analyzer against subset of metadata as it would not generate comprehensive report with how the objects are related to each other

If anyone had list of limitations with respect to Bladebridge can you please let us know the same

Re: Blade bridge Analyzer out of memory issue

Brahmareddy — Thu, 10 Apr 2025 02:55:47 GMT

Hi Vasu_Kumar_T,

How are you doing today?, As per my understanding, running out of memory with BladeBridge Analyzer can be tough, especially when you're working with large and complex metadata where you need the full picture. Even if you've increased RAM, the issue might still persist if BladeBridge tries to load too much metadata into memory at once, which is a common limitation when dealing with deeply linked objects. While there isn’t a detailed public list of limitations from BladeBridge, users have reported that handling large volumes of interconnected metadata (like thousands of objects with dependencies) can cause memory pressure, especially without proper tuning. One workaround could be to tune JVM heap size, check for heap space vs. metaspace limits, or split processing by object types if supported—even temporarily for analysis before stitching things together. You might also want to reach out to BladeBridge support—they’re usually responsive and can sometimes offer custom configs or batching options. Let me know if you want help drafting a support ticket or exploring JVM tuning options!

Regards,

Brahma

topic Re: Blade bridge Analyzer out of memory issue in Data Engineering

Blade bridge Analyzer out of memory issue

Re: Blade bridge Analyzer out of memory issue