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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
1 n  i! Q7 k+ @# \http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

8 L/ f9 G9 o) `2 {- ?Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

Larry Carpenter
" f# J. [* W8 N+ h# d( EAt 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
4 P7 G$ G, {2 \9 k- o0 R& ^6 {For 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
/ e& V' f2 t! V  co Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
! L! L, E  T$ @. Bo A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
$ t9 [, N7 |0 e& n  S  m• Cost Savings
5 p0 T+ t; r) M2 ~& g# h1 ?o Less waiting means less time wasted.
Quick 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.
See 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
; Z# s8 t; r  ~7 bCommon Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
$ |/ T0 H0 E" M7 }) f3 kDatabases – The Most Likely Culprit
( @7 D/ S4 o( d. h# t0 h• Database performance is highly sensitive to hardware, software, and DB configuration.
1 P5 _- {+ q6 {2 d3 ~; I6 ], N2 u• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
. r+ _% T$ N; d; J4 ~5 w6 i/ h8 I6 w• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
, {+ n8 w0 F# e' ?8 fMitigating Database Server Bottlenecks
• Must use dedicated DB server
" I* w  o' i2 q8 S* X  j( t  ^- ro 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.
8 \; F1 T8 V9 E" zo 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.
o Use disk controllers with a battery/flash backed cache.
4 Q% D% M- f0 R; Oo Use multiple disk controllers if possible.
• Cram the RAM
o 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.
% S5 }" J  h9 S1 M4 `8 d9 {' Z• 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.
; g* h9 g2 p: ]' F! [• DB maintenance tasks
- d; f, e6 X# Z& t1 lo Update statistics and rebuild indexes regularly.
% Z4 V/ U2 P& l# WCommon Teamcenter Server Bottleneck Causes
9 R3 W% g) r9 ^• Overloaded Tc Servers
2 }' v# z& H9 c3 [• Poor Web Tier Configuration
• Poor FMS Configuration
; T3 t# Y, J( o% m/ R4 ?+ S• Debugging Turned ON
• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
2 \* Z& @" {4 a. U* K1 M' `1 |  L• Put Dispatcher modules on separate computers away from other Tc Servers.
5 e: P& z+ D3 O* a7 w8 f0 m( V• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
5 t5 Y) R7 g7 Q+ x• 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.).
" i2 n0 i7 ?9 Z" F6 bo Set up multiple FSC cache servers to take load off busy volume servers/storage.
4 T# A9 x2 `8 E9 N9 x$ y) FWeb Tier Configuration
• Do not use port 80 or 8080
/ S8 v- l2 J  K& v) q3 U+ \" no 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.
  d9 H5 ^$ m7 h& w. a) ]* I• 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
4 A' l4 U" ?% J6 r- ko E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
+ O5 C# x! I$ L' D, S3 }! r• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common 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.
$ }$ E9 p9 f$ w• Using OOTB settings
o For development purposes only, remember?
7 F0 }. Q* f. y• Missing client IP address subnets
, P% T- |" b0 l" p- ?/ G• No load balancing
• Not using remote cache servers for WAN users
0 C* L, X& f2 ~0 ~$ Y& G; X6 o. @• Not using remote volume servers for WAN users
FMS Configuration
0 t# b5 k" `5 s5 K# m• Ensure routing is correct
o Between multiple FSC groups via entry/exit/link parameters
5 P" v& X  W7 w- lo Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
: R3 G6 T9 z! Z" g" v/ V' Ro Use correct transport algorithms for LAN and WAN users.
. R: A- y# @7 G$ i) ~• Tune FSC/FCC cache settings
& `' F5 n6 d+ V$ Ko Simply picking a total read/write cache size is not enough.
o 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.
5 A# F/ D$ B' Z; M# b0 W: lo Place client maps in the closest FSC group to their location.
• 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)
o Use redundant FSC cache servers to load balance each other. Also provides fail-over.
$ ~, U6 X2 l5 J1 C# ^8 ]( Z; e• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
9 C& y2 D3 I) C: s1 ^9 _: O& io 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.
( ~' @7 t  K, J( ?9 I1 K5 V• Prepopulate FSC caches
& X6 E  w) ~0 U$ T8 J1 g' ao Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
- f% x8 z& z2 _o TC_SECURITY_LOGGING=OFF
; p) G3 v% F" A9 d% q# G) K1 Oo TC_APPLICATION_LOGGING=OFF
" o$ w" P$ L9 P5 ?- O- }$ c0 Vo TC_SLOW_SQL=-1
3 T- ?5 O8 K! W1 K% _- H5 W% Z• 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).
- g0 i4 d( E- X' `% p% z* w1 J• Enable FCC File Warming
$ I" x) i5 v: \* C" ~9 T) eo Improve startup time by having FCC and Tc files pre-loaded at OS login.
2 k/ g" e/ B5 H6 r3 d8 r: WNetwork Performance
' y9 H2 @! W0 o4 ^/ w• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
; I6 N; b$ |8 |) X4 U) W# M• Optimize OS network settings
o OOTB settings are insufficient
o Applies to both servers and clients
7 c0 Q5 R' V8 Y& A! @5 zo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
Recommended Server Changes (Windows)
* V3 T5 t1 }* H4 N4 FSee Presentation.
Recommended Client Changes (Windows)
( T9 k1 ^2 B# ^* }  iSee Presentation.
Performance Monitoring Tools
) l) P8 e4 a* [" |  H& N• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
" D+ f* q# C; r6 Y• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
. n7 s: X* J3 Q; G• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
+ T* M- _+ E  p  }  ~- b• http://technet.microsoft.com/en-us/sysinternals/bb842062
/ J8 k- f* E) I2 LReference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
  X; c# S* D$ mo Teamcenter Network Performance Tuning
( G* e) Q  }- {- x( H" Go JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
1 N; \' t9 W5 m6 f• Oracle documentation & web sites
( V, T# `; _% }! Y4 n4 V• MS SQL Server documentation in addition to:
( i# K% {5 F. e' ^" Z( d/ `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 S: F8 f8 G9 @: x* b; u9 Vo Siemens Blog on Technet
/ b* O3 d/ w( W; N: h6 N" o http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
; @8 Z- [8 N2 O  \7 l5 f+ Ko Siemens-Teamcenter-SQL-Resource-Page
0 v2 m1 ]' B8 ]4 E' m9 c# D  f http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
- |. |" q2 Z9 {' w5 z* |9 ?• 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
9 ?7 k4 V- S0 ~# l$ T1 Qo Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
( m, c+ r" ]. h/ J. `Contact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
$ Q: j! `  D% J5 U0 }  FTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
1 ^! @1 @% o8 {4 v3 OAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
$ B1 `& w( x8 J) f

xiefeixiang

调优厉害啊

a150159

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