文本课件成果1

1、Turbo Charging TIBCO BusinessWorks - Tuning for Performance Mohamed Aariff April 11-13, 2006AgendaBW Message Flow Architecture Flow LimitMax JobsThread CountThread Count ImplicationsStep CountProcess and Activity DesignJMS Transport Questions *Circled numbers are tunable parameters.BW Message Flow A

2、rchitectureProcess Starters1Connections/SessionsThread Pool(for Job execution)4Thread Count5T1Binding|XSLT|ValidateActivityT2Binding|XSLT|ValidateActivityT3Binding|XSLT|ValidateActivityT-NBinding|XSLT|ValidateActivityStep Count Checkpoint databaseMax Jobs3Paged JobsReactivate.Dispatch Queue (ready j

3、obs)Job Pool (in memory).Ready/blocked stateQueueRecoverCheckpointOr pagedFlow Limit2Flow LimitLimits number of jobs created for a specific process.Protects BW engine against a surge in message load.Improves latency.Engine will resume creating new jobs when the sufficient number of current jobs have

4、 completed. Job Pool (in memory).Flow Limit2QueueProcess StartersFlow LimitConsiderations:Use when high-volume of ing messages and jobs are memory-intensive.Use when running out of memory is not acceptable during peak operation hours.Should only be used with protocols that can store the unsent messa

5、ges on the server (e.g., JMS, E-mail) until the BW engine can process them.If your protocol does not have high reliability, use flow limit only when you can tolerate message loss. Max JobsLimits the number of jobs stored in memory.Jobs created after max jobs limit will be paged out to disk.Engine wi

6、ll incur some overhead due to paging.Job Pool (in memory).QueueMax Jobs3Paged JobsPagedReactivateProcess StartersMax JobsConsiderations:Evaluate use of Flow Limit before considering Max Jobs.When there are many blocking activities (Wait for.) in a process Max Jobs can improve throughput.If your prot

7、ocol can not store the unsent messages on the server, use max jobs when you can not tolerate message lossIf the engine can handle peak message rate (no memory overflow issues), consider setting Flow Limit = 0 & Max Jobs = 0.Thread CountJobs are executed in a thread. Threads are the “worker-bees”.Thr

8、ead Count limits the number of threads that available to execute jobs concurrently. Set Thread Count value based on your environment (CPU, Memory, OS,.). Start with default value of 8, and double it until 90% CPU is reached.Thread Pool(for Job execution)4Thread CountT1Binding|XSLT|ValidateActivityT2

9、Binding|XSLT|ValidateActivityT3Binding|XSLT|ValidateActivityT-NBinding|XSLT|ValidateActivity.Dispatch Queue (ready jobs)Thread Count ImplicationsThread Count & Flow Limit.Threads will be under utilized when: S Flow Limit Thread Count. Thread Count & DB Connection.Set Maximum DB Connections = Thread

10、Count. If there is not enough database connections allocated, jobs will be blocked waiting for a free connection.Thread Count & JMS Session.When using client ack for JMS Receiver set the number of sessions higher than number of thread count.Step CountControls the number execution steps for a job bef

11、ore an engine thread switch occurs (Default is 20).Low value for Step Count causes frequent thread switching. This can lead to engine performance degradation.High value for Step Count causes the job to keep the thread for a long time. This can reduce the concurrency for executing jobs and inefficien

12、tly use the CPU.Does not apply for blocking activities (Sleep, Wait.).Considerations:High value can be favorable when there are large number of activities in a loop.Process & Activity DesignCall ProcessConsider using “Spawn” call process activity for heavy asynchronous process (such as logging). Thi

13、s will decrease response time (not CPU usage).Avoid passing large strings especially between spawn processes.Shared DataUse shared process variables to avoid data copying cost in call process.Consider using “Java Global Instance” shared resource, if the object can be shared by multiple jobs. Improve

14、s performance since the object is created once at engine startup.CheckpointsInvolves disk I/O. Therefore too many Checkpoints can result in performance degradation. Checkpoint in any called process (not spawned) saves the state of the process instance, including state of the parent process(es). Proc

15、ess & Activity DesignMessage & PayloadKeep XML structure & schema as simple as possible.Consider re-architecting the XML schema with XML elements that contain nested elements of nested elements.MappingUse “Mapper” instead of “Transform XML Activity” wherever possible for a better performance.Dont ev

16、aluate the same expression many times (especially if the data is large). Use a variable instead to only evaluate it once.Use “for-each” in the Mapper instead of an iterate group when possible.JMS TransportExplicit vs. Client Acknowledgement (Ack)Use Explicit Ack for TIBCO EMS. It uses a single sessi

17、on to receive multiple messages and provides more efficient resource usage.Client Ack is JMS Standard. Configure multiple sessions to receive messages faster; set number of sessions higher than number of engine threads.Message Type Processing Overhead Low: Simple, Text, BytesMed: Map, Stream, XMLText, Object ReferenceHigh: ObjectJMS TransportWhen using Client Ack, confirm messages as soon as possible to improve throughput.Use JMS Queue Sender and Wait For JMS Queue Message activities instead of the JMS Queue Requestor activity to potentially improve throughput.If possible choose NON_PERSIS