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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
7 V' P; u: _% n! w* L0 Ehttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

  @) u4 H% H; O; B, d( B5 WTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

Larry Carpenter
( y: q) U* {8 r8 y$ d' n- U  R( [9 jAt 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
For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
, I; L/ _  G5 B, q' P- Y" IWhy Performance Matters
9 O1 b4 x9 D, b( F' B$ I: X7 m• Productivity – doing more work with less
o Improve end user productivity
o Improves administrator productivity
  X, n( x+ @# O  t. E3 }2 f fewer help desk calls responding to or fixing preventable problems
& c' [3 c3 e7 G' r( d( @) D. o5 q$ j• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
4 g! n- l+ y' T! \, o4 zo Less opportunity for data corruption
7 v" j# v- ~1 A+ yo Fewer operational errors/problems
! T" r. {  h1 d: S• Cost Savings
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.
1 n1 l! g- Q! H: X* [& nSee 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
$ @# Y0 s* h2 q1 JCommon Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
* n5 G7 w4 q! u6 POverloaded 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.
8 d! l4 I* @0 V" l( p1 x5 ~Databases – The Most Likely Culprit
7 i$ e' D. e3 D0 O/ x8 U0 C2 C* K! I. l: G• Database performance is highly sensitive to hardware, software, and DB configuration.
6 ~4 T3 U3 [2 j- W$ a. S2 k* B• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
# `# t2 X/ C7 a; N* ^/ ]• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
9 j$ B; Q5 s. o/ @' j  X. aMitigating Database Server Bottlenecks
9 d! b; Z, K( w: v! Q• Must use dedicated DB server
o Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
( ?6 v, d* Z4 z. P/ f• Must have fast dedicated storage for DB files
, _+ E, j; R5 P# w, To Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
7 H( L% v2 H4 ~- _/ go 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.
% b; d; e0 Y  Z, ?" Vo Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
• Cram the RAM
' ~, l1 L! c2 K  n' [- u5 vo 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.
2 D3 i/ D- c/ F• 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
1 D, L2 I; k( d5 r$ X4 N0 u2 Uo Update statistics and rebuild indexes regularly.
0 G# k1 U( M& t+ T8 S) B& ECommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
6 J( S0 S, Q& F" m5 ~8 }' V• Poor Web Tier Configuration
) v# B  u7 B# A( I• Poor FMS Configuration
• Debugging Turned ON
9 e' a' i8 f" S9 k/ s( Z" R• Rich Client using OOTB settings
5 v7 Q3 O( [, n3 @2 X: b; L‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
' p6 K0 M: G: d  _4 [+ f7 _: q• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
5 s) n6 o/ G% n/ E2 ^* T• Use load balancing for Middle Tier & FMS:
! S3 O* S8 p6 M  k2 `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.
+ j0 p  n' D: x* w) r8 F/ WWeb Tier Configuration
• Do not use port 80 or 8080
: w; p+ h0 N# a+ Ro 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.
& o; l8 r' S6 m2 {) R1 x, V, w• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
+ B/ y( |- a& g• Change/tune OOTB settings for Web Server/App
, {% `, D  T4 s! t& W4 Fo E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
" V* A. u# s  k3 G6 o4 io 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.
• Using OOTB settings
o For development purposes only, remember?
3 H* q% E6 S# |9 L6 b7 e- T• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
! a# @" t% [; ]# E0 _• Not using remote volume servers for WAN users
4 D, k! \7 D* A" q/ ^; bFMS Configuration
• Ensure routing is correct
o Between multiple FSC groups via entry/exit/link parameters
' N+ Z2 D2 E6 g8 g+ Ao Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
) @3 e/ |: \# q% Vo Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
9 _: J1 X* Z4 K( o: r! |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
5 b2 Y4 L. }9 Y% H& H+ m• 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.
• Use multiple FSCs for load balancing
5 i+ i' V$ C. N7 h; P1 go Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
. g5 q) |' |% b* g5 l, X  N' ?4 |o Use redundant FSC cache servers to load balance each other. Also provides fail-over.
• Place FSC cache servers close to users
. p, x0 h0 k: A/ n% jo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
, ]( ]! u8 q# v• Place Volume servers close to users
  f  {. @: b6 K; Y0 _! to 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.
) _8 m9 ]# o. M) Q7 w• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
" p0 Z5 m# i8 g3 W2 V9 C) VMisc Teamcenter Changes
) d' y8 T$ N9 `8 q, Q; S* h+ K• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
6 ?# j& w: k* f+ k  s! i0 r- fo 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).
• Enable FCC File Warming
) i$ y7 _+ {1 K# C$ o( O" E8 lo Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
' R. d9 F; p; k; f$ b& \• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
& N4 K, ]' G. e& Oo If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
• Optimize OS network settings
- z7 ?1 N* a( Io OOTB settings are insufficient
7 C3 _! S* G7 z# A/ D# ?+ N3 b; jo Applies to both servers and clients
o Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
, g3 Z* ]- ^5 l9 o4 FRecommended Server Changes (Windows)
& r% r! U/ O3 ^6 KSee Presentation.
Recommended Client Changes (Windows)
9 r$ i; [6 H3 A* \+ D! \; zSee Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
- i) {- M' w4 ^' p• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
3 H& w) ~+ Y) t/ R# V: V• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
o 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
; i# N# Z/ h6 s; l. e4 Y& B• MS SQL Server documentation in addition to:
$ h5 \( p* r; L. E# ]5 Qo Best Practices for Running Siemens Teamcenter on SQL Server
+ X7 d, I0 v( S) j0 c http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
o Siemens Blog on Technet
: J* w7 L3 z8 U# |' B' h http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
 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
1 J# }1 p* O' P& [; {o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
Larry 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
' E1 W0 i  C% cAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

5 I+ d  B8 Y/ i

xiefeixiang

调优厉害啊

a150159

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