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
