locked
Host throttling RRS feed

  • Question

  • Guys,

    In my application, Biztalk receives files through file adapter. Each file has 500 records and I'm using xml disassembler to split them in to records in pipeline.

    Now I have a question, if I want to receive ~ one file per minute, in Message Publishing Throttling Settings (For File Adapter Host), to set Minimum number of samples, Sampling window duration (milliseconds), Rate overdrive factor (percent), Maximum throttling delay (milliseconds), should I consider records as samples or files as  samples?

    Means, Considering Files as Samples____Minimum number of samples == 1, Sampling window duration (milliseconds) == 60,000, Rate overdrive factor (percent)==100%, Maximum throttling delay (milliseconds) == 300,00,000 or ~8.5 hour.

    Or I need to consider Records as sample and put Minimum number of samples == 500 and all other things as shown above.

    Thanks, Rik

    Monday, August 8, 2011 1:05 PM

Answers

  • Hi Rik,

    It is true that it does clarify (make a distiction) frequency (number of documents) and size (number of records). So you will have to test values for having one document per minute i.e. 1 document per minute that results in publishing 500 records, so I would say you assumption is correct (Records as sample and put Minimum number of samples == 500). Still I would test it first.

    HTH

    Regards,

    Steef-Jan Wiggers
    MVP & MCTS BizTalk Server 2010
    http://soa-thoughts.blogspot.com/
    If this answers your question please mark it accordingly


    BizTalk
    Monday, August 8, 2011 1:37 PM
    Moderator
  • Not sure you can do this with the host throttling. It architected to do different kind of throttling. Not to set up delays.

    I've implemented something like you want to. See this article "using orchestration for throttling"


    Leonid Ganeline [BizTalk MVP] BizTalk: Sample: Context Routing and Throttling with orchestration
    Monday, August 8, 2011 11:08 PM
    Moderator

All replies

  • Hi Rik,

    Minimum number of messages BizTalk Server will sample for the Sampling window duration before considering rate-based throttling. If the actual number of samples in a sampling window fall below this value then the samples are discarded and throttling is not applied. This value should be consistent with a rate at which messages can be published under a medium load. For example, if your system is expected to handle 1,000 documents per second under a medium load, then this parameter should be set to 1,000 * Sample window duration in seconds (or more precisely, 1 * Sample window duration (milliseconds)). If the value is set too low, then the system may experience a throttling condition under low load. If the value is set too high, then there may not be enough samples for this technique to be effective.

    For reference see http://msdn.microsoft.com/en-us/library/dd761093.aspx

    HTH

    Regards,

    Steef-Jan Wiggers
    MVP & MCTS BizTalk Server 2010
    http://soa-thoughts.blogspot.com/
    If this answers your question please mark it accordingly

     


    BizTalk
    Monday, August 8, 2011 1:22 PM
    Moderator
  • Steef-Jan Wiggers,

    I went through those MSDN documents before but there is not clear indication to use number of files as samples or number of records as sample (I'm using File adapter, Receive pipeline with XML Disassembler to split file into records, each file has 500 records)?

    Let me eaplain my scenario again, I want to receive One File per Minutes, What values I should put for throttling? Other thing to consider here is, I'm splitting file into records in receive pipeline, so should I use records as number of samples or files? None of the document/s states that.

    Thanks, RIK

    Monday, August 8, 2011 1:28 PM
  • Hi Rik,

    It is true that it does clarify (make a distiction) frequency (number of documents) and size (number of records). So you will have to test values for having one document per minute i.e. 1 document per minute that results in publishing 500 records, so I would say you assumption is correct (Records as sample and put Minimum number of samples == 500). Still I would test it first.

    HTH

    Regards,

    Steef-Jan Wiggers
    MVP & MCTS BizTalk Server 2010
    http://soa-thoughts.blogspot.com/
    If this answers your question please mark it accordingly


    BizTalk
    Monday, August 8, 2011 1:37 PM
    Moderator
  • Steef-Jan Wiggers.

    Thanks..I will certainly test it to see.

    Monday, August 8, 2011 1:55 PM
  • Not sure you can do this with the host throttling. It architected to do different kind of throttling. Not to set up delays.

    I've implemented something like you want to. See this article "using orchestration for throttling"


    Leonid Ganeline [BizTalk MVP] BizTalk: Sample: Context Routing and Throttling with orchestration
    Monday, August 8, 2011 11:08 PM
    Moderator
  • Right, Host throttling doesn't directly delay processing but we can achive processing delays indirectly by throttling the hosts, that means if I put Number of sample == 500 and Sampling window duretion == 1 minutes. We just delayed rest of samples by 1 minutes.
    Tuesday, August 9, 2011 1:45 PM
  • Right, Host throttling doesn't directly delay processing but we can achive processing delays indirectly by throttling the hosts, that means if I put Number of sample == 500 and Sampling window duretion == 1 minutes. We just delayed rest of samples by 1 minutes.

    Did you try this?
    Leonid Ganeline [BizTalk MVP] BizTalk: Sample: Context Routing and Throttling with orchestration
    Wednesday, August 10, 2011 4:47 AM
    Moderator
  • Haven't got chance yet.
    Tuesday, August 16, 2011 5:43 PM