BizTalk 2006 R2 EDI流水线处理速度 [英] BizTalk 2006 R2 EDI Pipeline Processing Speed

问题描述

大家好，

我正在开发一个接受HIPAA 834文件的流程，以便从我们的客户那里获得会员维护。我正在处理834个文件，其中最多可包含100万个成员。这些显然是巨大的文件，大小可以从200 MB到1 GB不等。我试图弄清楚有哪些可用的选项可以增加从834文件到事务的xEDI表示的转换时间。 BizTalk似乎在发送xEDI之前处理内存中的整个文件。我假设它以这种方式工作，以便在传递xEDI并创建997响应事务之前知道文件是否为vaild。

< p align = left>我的问题是可以使用性能调整设置还是物理硬件来实现，以允许BizTalk提高解析834文件的速度？我确保通过将进程内存使用率设置为0并将物理内存使用率设置为0以及关闭基于速率的限制来确保不会受到限制。无论哪种方式，BizTalk似乎都没有利用更多可用的物理内存。当服务器可以使用超过2GB的内存时，

BTSNTSvc.exe进程的内存使用量不会超过300MB。我还测试了不同的CPU配置，范围从1个CPU到4个CPU。在任何一种情况下，通过向BizTalk服务器添加更多CPU，它似乎只会在CPU上传播处理时间，并且不会以更快的速度转换文件。

这只是EDI管道的限制，因为它只能以一定的速率转换EDI 834文件，无论我能为服务器提供多少物理功率？

任何帮助/想法都将不胜感激。

谢谢，

Joel

解决方案

BizTalk EDI管道使用流式传输，因此不会将所有msg加载到内存中。它会等到处理文档以生成997s。

我可以与其他人核对成员，如果我有任何信息，将分享

Hi all,

 

I am developing a process to accept HIPAA 834 files for membership maintenance received from our clients. I am dealing with 834 files that can up to 1 million members within them. These are obviously huge files and can vary in size from 200 MB to 1 GB. I am trying to figure out what are some possible options available to increase the translation time from the 834 file to the xEDI representation of the transactions. BizTalk seems to process the entire file in memory before sending out the xEDI. I assume it works this way so as to know if the file is vaild before passing out the xEDI and creating the 997 response transaction.

 

My question is what can be done with either performance tuning settings or physical hardware to allow BizTalk to increase the speed at which it can parse the 834 file? I have made sure that I am not being throttled by setting the Process memory usage setting to 0 and Physical memory usage to 0 as well as turned off rate based throttling. Either way BizTalk doesn't seem to take advantage of more physical memory made available to it. The

BTSNTSvc.exe process doesn't go much over 300MB of memory usage when the server has over 2GB of memory it can use. I have also tested in different CPU configurations ranging from 1 CPU to 4 CPUs. In either case by adding more CPUs to the BizTalk server it just seems to spread the processing time accross the CPUs and doesn't translate the file at any faster rate.

 

Is this just a limitation of the EDI pipeline in that it can only translate EDI 834 files at a certain rate no matter how much physical horsepower I can make available to the server?

 

Any help/ideas would be appreciated.

 

Thanks,

Joel

解决方案

The BizTalk EDI pipelines use streaming and hence dont load all the msg into memory. It does wait until the doc is processed to generate the 997s.

 

I can check with other members and if I have any info, will share

这篇关于BizTalk 2006 R2 EDI流水线处理速度的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！