Microsoft Knowledge Base Email Alertz

The BizTalk Interchange Interface is used to exchange documents between an application and BizTalk Server 2000 either directly or through a Receive function. When you use the Interchange.Submit method to submit a document that uses the Document...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 287538 - Last Review: October 10, 2003 - Revision: 3.0

BizTalk Interchange.Submit is Slower when Processing a Document from Memory

This article was previously published under Q287538

On This Page

SUMMARY

The BizTalk Interchange Interface is used to exchange documents between an application and BizTalk Server 2000 either directly or through a Receive function. When you use the Interchange.Submit method to submit a document that uses the Document parameter as a string in memory you may find that the document is processed 3-5 times slower than if the Document parameter were passed as a FilePath (read from disk).

MORE INFORMATION

When BizTalk Messaging reads in a file, the file is memory-mapped so that it never gets loaded into memory all at once. The file is read as necessary by the component until the data is available off of the physical disk. Passing the data into memory data makes the data that much larger because:

  • The file must be loaded into a string that is large enough to hold the file.

  • If the file data is non-Unicode, the data size is doubled because of the conversion to Unicode.

  • There is the cross-process marshalling of the data.

  • If this is flat file data, the conversion to XML suffers a 2x to 3x expansion in data size (a sparse flat file data is less).

STATUS

This behavior is by design.

APPLIES TO
  • Microsoft BizTalk Server 2000 Standard Edition
Keywords: 
kbinfo kbpending KB287538
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate