Throttling state

Use the following steps to access the performance counters.

On the Desktop, click Start, point to Programs, point to Administrative Tools, and then click Performance.

In the Performance dialog box, click Add.

In the Add Counters dialog box, from the Performance object drop-down list, select from the available BizTalk:Message Agent performance counters, and then click Add.

In the Add Counters dialog box, do one of the following:

After selecting the counters, click Add and then click Close.

For each Host instance,the throttlings state are shown with « Message delivery throttling state » and « Message publishing throttling state »

When there is no throttling, their values are 0. But when they got throttlhing state, their value could be 1 to 11

Here is their definition :

Message delivery throttling state A flag indicating whether the system is throttling message delivery (affecting XLANG message processing and outbound transports).

  • 0: Not throttling
  • 1: Throttling due to imbalanced message delivery rate (input rate exceeds output rate)
  • 3: Throttling due to high in-process message count
  • 4: Throttling due to process memory pressure
  • 5: Throttling due to system memory pressure
  • 9: Throttling due to high thread count
  • 10: Throttling due to user override on delivery
Message publishing throttling state A flag indicating whether the system is throttling message publishing (affecting XLANG message processing and inbound transports).

  • 0: Not throttling
  • 2: Throttling due to imbalanced message publishing rate (input rate exceeds output rate)
  • 4: Throttling due to process memory pressure
  • 5: Throttling due to system memory pressure
  • 6: Throttling due to database growth
  • 8: Throttling due to high session count
  • 9: Throttling due to high thread count
  • 11: Throttling due to user override on publishing

For fixing throttling, start by readung this link http://msdn.microsoft.com/en-us/library/aa559893(BTS.10).aspx

Then I wish you luck

Persistence points, tired to repeat it

Often ignored, but a really important, persistence points in Biztalk are the key issue in dealing with Orchestration Performance. Many applicative problem come from a misunderstanding of this concept.

Sandro perreira (a great biztalk MVP) wrote a great article about it : http://sandroaspbiztalkblog.wordpress.com/2009/10/23/biztalk-orchestration-%E2%80%93-understanding-persistence-points/

You should read it,

All BizTalk developper must be careful to those concepts and organize their developpement around it.

A common mistake is the send port in a while shape, more than 50 send don’t forget to use atomic scope.

Another one, be careful with custom c# object and the serialization way.

Really interesting.

BTS high availability

Microsoft gives a great articles’ serie about High availability in BizTalk. They provides a lot of advice when installing a very stressed BizTalk environment;

Some concerns SQL, and other windows environement, but all are required; in my experience, I always followed this requirements.

MSDN

MDSN is a huge online repository for Microsoft documentation. This should be your primary source for information on BizTalk availability:

Articles

The following articles provide more information on High Availability for BizTalk:

Blogs

The following blog posts by community provide more background information and experience on High Availability for BizTalk:

Webcasts

The following web casts by community provide more background information on High Availability for BizTalk:

See Also

source : http://social.technet.microsoft.com/wiki/contents/articles/6532.aspx

WCF custom vs WCF with IIS

In a previous blog entry, I wrote about exposing wcf port without IIS. But now when I use IIS and when I don’t use it ?

Actually, when I use IIS I’ve got a new technic layer and increase the resource used.


So what IIS bring more.As we can see with or without IIS doesn’t influence response time (click on the picture to zoom). Lire la suite