Download presentation
Presentation is loading. Please wait.
Published byKolby Tapper Modified over 10 years ago
3
This picture has been released into the public domain by its author, ChiemseeMan at the German Wikipedia projectpublic domainChiemseeManGerman Wikipedia
8
Configure Test Setup BizTalk Server Best Practices Analyzer BizTalk Benchmark Wizard BizTalk Server 2009 Performance Optimization Guide
9
netTcp Passthrough WCF One-Way Send port netTcp Passthrough WCF One-Way Receive Location BizTalkMsgBoxDb Received msgs/sec Processed msgs/sec BizTalk Benchmark Wizard The Back-end service
10
# of Bts Srv #CPU/Bts Srv # SQL Srv#CPU/SQL SrvMsgs/Sec 11 Quad(1) 200 11 Quad1 350 11 Quad12 Quad490 12 Quad1 700 21 Quad12 Quad770 22 Quad1 910 22 Quad14 Quad980
12
BizTalk BizTalk performance SQL SQL performance Storage Storage performance But Im a Developer!!! I am not meant to know about this stuff. The X department take care of that.
13
the BizTalk guythe SQL guythe Storage guy I like to order a SQL cluster with 12 disks... I like to order 12 LUNS... Ill let him share the disk array with the SAP system..
15
Eliminating bottlenecks Data Log
16
Datafile PFS Page
17
Data Data Data Data
18
Primary (default file group) Primary (default file group) Misc Data Misc Indexes Predicate Data Predicate Indexes Message Data Message Indexes For more information:BizTalk Server MessageBox Database Filegroups SQL Script
20
Datafile * * * * *
21
EXEC sp_tableoption N'Parts' 'text in row','4000 EXEC sp_tableoption NSpool' 'text in row','4000 EXEC sp_tableoption N'DynamicStateInfo_[HOST]' 'text in row','4000' *There are one DynamicStateInfo table per host.
24
Data Data Data Data
25
Base casting Spindle Slider (and head) Actuator arm Actuator axis Actuator SATA interface connector Power connector Flex Circuit (attaches heads to logic board) Platters Case mounting holes Cover mounting holes (cover not shown) Performance: 200-250 IO Per Second (IOPS)
26
No moving parts! Performance: 4000-4500 Read IO Per Second (IOPS) Less writes! 1500 Write IOPS
27
Latency (response time) Reads are in the 5-6ms range and writes 1-2ms with spikes to 20-30ms during checkpoints. Checkpoint Activity These are short-lived burst of writes with a large amount of outstanding I/O requests. It is normal for latency to increase a bit during this operation. Hosting BizTalk databases on poor performing disks, a SQL checkpoint can cause a message processing drop. High throughput storage for SQL Server data and log files is absolutely critical to BizTalk performance.
28
By partitioning < 50% of the disk, the data will be allocated on the outer track, making all reads and writes done from outside edge. Example: A 1 TB disk with an access time of 12 ms at 200 IOPS ~ throughput of 100 MB/s A 300 MB partition from the same drive might end up with an access time of 6 ms at 300 IOPS ~ throughput of 200 MB/s * *For sequential workloads this can be even higher Partition
29
CPU PCI Bus I/O Controller / HBA Cabling Array Cache Spindle Windows SQL Serv. DB Key Takeaway: This is NOT going to be easy…
30
Disk Array RAID 5RAID 10 LUNLUN LUNLUN the Storage guy Ill let him share the disk array with the SAP system.. Key Takeaway: There might be a conflict of interest…
31
RAID 1 (Mirroring) + Total data redundancy - Slow - Expensive RAID 5 (Distributed parity) + Cost efficient + Fault-tolerant + Good performance - The extra time required to calculate and store parity degrades the write performance RAID 10 (1+0) (Mirroring + Spriping) + Total data redundancy + Increased write transfer rate - Expensive RAID 0 (Striping) + Very fast - No redundancy
40
This picture has been released into the public domain by its author, ChiemseeMan at the German Wikipedia projectpublic domainChiemseeManGerman Wikipedia
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.