138. 解决teamcenter性能差的建议----值得学习!!!!

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
$ k% X# I; x5 |8 H0 fhttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
% p% Y% S; K2 ?; s
Larry Carpenter
At the Chicago-Wisconsin RUG Fall Conference in October 2012, I gave a presentation on common Teamcenter performance issues and solutions along with listing, in one place, many other past Teamcenter performance presentations and white papers. It was very well received by a standing room crowd, so I thought I'd share it with the rest of the PLM World community. Here is a link to the presentation (you must be a TCUA SIG member to view it):  http://www.plmworld.org/p/do/sd/sid=3758&type=0
$ q6 f+ M/ ^7 z! W+ E0 S  P8 H! n% yFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
Why Performance Matters
• Productivity – doing more work with less
o Improve end user productivity
o Improves administrator productivity
2 E' E" A: A% V$ ^1 q& a fewer help desk calls responding to or fixing preventable problems
• Reliability
# q: q( [; f- q, u& Fo A well tuned Teamcenter environment also improves system stability and uptime.
; }  ^! I% z$ W+ L& O7 {o Less opportunity for data corruption
1 F, P/ J! C2 R# vo Fewer operational errors/problems
• Cost Savings
" P+ N5 O- r6 H1 G% r* ao Less waiting means less time wasted.
% n0 x$ M8 U0 {7 K7 d" fQuick Case Study: Company ‘S’
Performance was so bad that something which used to take 10 minutes was taking 2 hours to do.Did pretty much everything wrong, performance-wise, at first but ultimately fixed every major problem. What took 2 hours now only takes 2 minutes.
) R, P& i' K6 K: E* {& zSee my March 2012 article on PLM World’s website for details:
Teamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
Common Performance Bottleneck Causes
6 q/ z7 O" G8 v' a& UUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded servers — Putting too much on a single server.
$ V8 `/ n* V' p+ B9 i' \' H1 NOperating system settings — Network settings most common (e.g. TCP parameters).
! R" z% H& `2 d% wLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
# R1 G4 |6 D2 o( A1 n0 V% aDatabases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
, u  j, c. Y1 @) Q3 w$ X7 g• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
2 Y" n5 x$ K; g; T, o* \/ JMitigating Database Server Bottlenecks
5 f+ l# f4 k5 C7 J. c• Must use dedicated DB server
8 p/ Q3 T% U, {: Uo Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
• Must have fast dedicated storage for DB files
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
o Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
2 v1 q/ i% ~. L8 g9 D8 F% ^o Use disk controllers with a battery/flash backed cache.
2 A6 V, b( N% A3 a3 N7 ro Use multiple disk controllers if possible.
• Cram the RAM
: B) q1 s9 G' H5 a2 c2 x- do Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• Use 64-bit OS & DB software
o 32-bit software has severe limitations regardless of whether you use “/3G”, AWE, or PAE settings to access memory beyond 3-4G. It’s still a bottleneck.
9 h, w" ^4 s7 c* k! Y# j• Use a good quality network adapter(s)
o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
. j) E: J+ T( d8 M0 g$ V  Y7 E• Poor Web Tier Configuration
4 J1 r0 u4 A. i9 G• Poor FMS Configuration
• Debugging Turned ON
• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
" }5 Z9 A) W5 d• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
o Use multiple Web/Enterprise Tier servers to open up potential hardware resource bottlenecks (e.g. CPU, RAM, network adapter I/O, disk I/O, MB bus, etc.).
o Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
3 {7 r5 F& ?4 h5 H7 }$ K; R3 f• Do not use port 80 or 8080
o HTTP traffic on those ports is considered web browsing traffic and is therefore given lowest priority on any network. Can also cause randomly dropped connections.
• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
: Q& [1 d3 N. ?1 A; v! No E.g. timeout values, max # of threads, Java memory, etc.
, L# A+ A4 D5 O8 }0 ?o Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
; O! p9 @3 \+ G& l  Zo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
" i$ D3 Z; F6 \! F& v+ C  P9 M- cCommon FMS Bottleneck Causes
• Data improperly routed
o E.g. Forcing data to go through a remote FSC server over a WAN and back again over the same WAN instead of simply pulling it directly from a nearby Volume/cache server.
• Using OOTB settings
o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
! [. B4 P8 C1 b+ D  h1 `$ v0 o: s• Not using remote volume servers for WAN users
1 D7 F% s3 A6 D3 ~0 }& R' ?FMS Configuration
• Ensure routing is correct
: z' V7 I9 J/ [o Between multiple FSC groups via entry/exit/link parameters
o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
o Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
: `  s; F3 _3 ]. Zo Simply picking a total read/write cache size is not enough.
4 H  ]" z( A8 v3 bo Read “Sizing the FMS fast cache” in the Teamcenter help documentation. There is also a FMS cache sizing tool available from the GTAC web site. Link to FMS Calculator
• Ensure correct client maps
o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
o Place client maps in the closest FSC group to their location.
9 J3 V/ i. g% M) D( a2 Q• Use multiple FSCs for load balancing
o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
& o2 e( t5 W9 |/ io Use redundant FSC cache servers to load balance each other. Also provides fail-over.
, }# Z: Y! T2 ?2 Q: P1 z4 A; _• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
9 j) Q4 Q- `! f: u7 z9 w% b9 g• Place Volume servers close to users
o Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
o Greatly improve write performance (save time) over a WAN especially for CAD data.
9 X. W6 H3 L2 z' x• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
6 d5 r9 W) ~, `; z  ^5 p7 |6 g$ JMisc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
o Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
' D' C6 O( y2 h' M• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
0 {, v; N2 W- X2 p, NNetwork Performance
7 s, `1 S  l2 q. A8 G# }' i• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
6 }! M7 `2 ^0 Ho If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
8 o9 T! n" f* e7 v  s• Optimize OS network settings
9 L: {! s8 H+ u& b+ S  U: Po OOTB settings are insufficient
o Applies to both servers and clients
. l) g& u4 J* ~& ?7 L) g: r- Q2 ]% Zo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
6 S! E5 m' Z1 i6 f3 J8 ], p; KRecommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
0 S4 h3 ^' G) }) j  \- a  q  fSee Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
. i( E+ x/ B3 O$ y2 v% y6 J3 I• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
4 i4 m5 ~5 F) K( b8 Z5 d0 Y8 ~• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
( U8 d* I1 K* M" Y3 [' H• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
3 _" ~4 y: P/ g' j8 {$ P+ BReference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
: x0 N. P0 e: Q& z4 K- uo Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
• Oracle documentation & web sites
+ T+ v! B0 l8 W+ d7 t7 e/ v8 O$ k• MS SQL Server documentation in addition to:
o Best Practices for Running Siemens Teamcenter on SQL Server
 http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
6 k5 e; M9 J+ Q( I4 Vo Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
% [. N8 w, a9 v  G http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
" }4 A& v; h8 k. N; B8 p( Ao Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
1 I/ W/ {- K+ r1 N) W  b4 BLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
8 |1 `+ k- V/ B8 @, c5 ?Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
# r+ ~1 e0 q# W7 H7 ]- T; h
7 @. _9 R- V) ^/ c1 Y+ C

xiefeixiang

调优厉害啊

a150159

总结全面，我们也是类似情况，找了西门子的团队过来优化的