|
Home > Archive > BizTalk Server General > May 2006 > BizTalk Server Hardware Spec
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk Server Hardware Spec
|
|
| Nick K. 2005-12-05, 5:55 pm |
| I have been asked to spec out the hardware for a Windows 2003 Server that
will be used to run BizTalk 2004 or 2006.
This server(s) will be processing large EDI 811 files and mapping those to
XML files. There will be a lot of files and they may be large.
Any recommendations?
| |
| BizTalk Benjamin 2005-12-06, 5:54 pm |
| Hi Nick,
If you can afford it, I'd say go for a large RAM spec even max it out at 8GB
RAM because the XML processing is really memory intensive.
In terms of CPU's though, remember that you will need a license per
processor. A while ago someone here posted that they had a single processor
license running on a dual CPU box with hyperthreading (equiv to 4
processors)and found that the engine actually throttled down the performance
to 25% each giving them only what they paid for. Nobody from MS clarified
this as behavior by design but its certainly an interesting scenario.
BTS can handle really large files but you do need to consider debatching
options to keep sizes optimal and fast. Take a look at Matt Meleski's series
of posts on the subject (eg:
http://objectsharp.com/blogs/matt/a...10/23/3525.aspx)
If you have a situation where a supplier comes on board sending you a huge
first load of data and afterward the regular updates are of medium size, you
may have to do put in some additional components or a different route to
handle the initial data load. We had issues with this where we got 90MB text
files that ended up getting mapped into 150MB XML files but when sent to our
database via a WebService, caused HttpTimeouts, msg size issues etc.
HTH
Benjy
"Nick K." wrote:
> I have been asked to spec out the hardware for a Windows 2003 Server that
> will be used to run BizTalk 2004 or 2006.
>
> This server(s) will be processing large EDI 811 files and mapping those to
> XML files. There will be a lot of files and they may be large.
>
> Any recommendations?
>
>
>
| |
| Doug Girard [MSFT] 2006-05-29, 5:21 pm |
| Nick,
These links should help with your capacity planning:
http://msdn.microsoft.com/library/d...-us/BTS06Concep
tsPlanning/html/9a7c3e7e-df6d-4ec2-9879-cb234386cd71.asp
http://blogs.msdn.com/biztalkperformance/
Regards,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: BizTalk Server hardware Spec
>thread-index: AcX6l4tBN8mOj43tT3q227UyMAnD5g==
>X-WBNR-Posting-Host: 84.9.47.134
>From: "=?Utf-8?B?Qml6VGFsayBCZW5qYW1pbg==?="
<BizTalkBenjamin@discussions.microsoft.com>
>References: <eas7z#e#FHA.2916@TK2MSFTNGP10.phx.gbl>
>Subject: RE: BizTalk Server hardware Spec
>Date: Tue, 6 Dec 2005 11:02:03 -0800
>Lines: 40
>Message-ID: <C666ED1B-BE07-4975-8A1A-E6FCB0A1D562@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.biztalk.general:33179
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>Hi Nick,
>If you can afford it, I'd say go for a large RAM spec even max it out at
8GB
>RAM because the XML processing is really memory intensive.
>
>In terms of CPU's though, remember that you will need a license per
>processor. A while ago someone here posted that they had a single
processor
>license running on a dual CPU box with hyperthreading (equiv to 4
>processors)and found that the engine actually throttled down the
performance
>to 25% each giving them only what they paid for. Nobody from MS clarified
>this as behavior by design but its certainly an interesting scenario.
>
>BTS can handle really large files but you do need to consider debatching
>options to keep sizes optimal and fast. Take a look at Matt Meleski's
series
>of posts on the subject (eg:
>http://objectsharp.com/blogs/matt/a...10/23/3525.aspx)
>
>If you have a situation where a supplier comes on board sending you a huge
>first load of data and afterward the regular updates are of medium size,
you
>may have to do put in some additional components or a different route to
>handle the initial data load. We had issues with this where we got 90MB
text
>files that ended up getting mapped into 150MB XML files but when sent to
our
>database via a WebService, caused HttpTimeouts, msg size issues etc.
>
>HTH
>Benjy
>
>
>
>"Nick K." wrote:
>
that[vbcol=seagreen]
to[vbcol=seagreen]
>
|
|
|
|
|