BizTalk processing HI - 64 bit and memory usage

Question

Hi,
This is about our BizTalk 2006 R2 in production env. I have the processing host as 64 bit. We do not have sudden heavy loads ; but we have consistent activity. I noticed that the memory usage in windows task manager for the processing HI gradually increases...to above 1GB and keeps growing.

Earlier we had the same applications on 32 bit HI on different server. But i never saw it increasing like this.

I have ruled out huge maps,functoids, transformations related to memory loss. The applications across both servers are the same. The only thing that has changed is the HI from 32bit vs. 64bit.

Has anyone faced this situation or noticed this? How do i troubleshoot this?

Thanks!

Answer 1

I dont think this is a problem due to 64 bit change. Are you getting any errors in the Error log? Are there any suspended messages?

---

Abdul Rafay http://abdulrafaysbiztalk.wordpress.com/ Please mark this as answer if it helps

Answer 2

No. I am not getting any errors or suspended messages.

Everything is working as usual.

Answer 3

You could try setting the host to 32-bit only to see if you get the same memory management like on the 32-bit server.

With BizTalk you do have some adapters and services that can only run under 32-bit so these processes will be processed through Windows on Windows (WOW) so this may account for some of the additional RAM consumption. The RAM consumed by the WOW processing may still exist even if you mark the host as 32-bit.

This is just a guess but it seems possible.

Thanks,

---

If this answers your question, please use the "Answer" button to say so | Ben Cline

Answer 4

Ben,

Thanks for you suggestion. I captured some memory usage statistics before converting the HI to 32 bit.

So that i will have something to compare..and i will post back here what i find.

Thanks!

Answer 5

I did find out that converting the FILE/MSMQ adapters as 32 bit made a HUGE difference.

The memory usage stats remained very consistent.

There is something out there with the FILE/MSMQ handshake that results in higher memory footprints when coupled with the 64 bit HI.