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
3 h2 V8 @" i# ]/ T) n4 whttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
% _' [, z/ ]: S- z
Larry Carpenter
6 T9 G. H$ E0 g' o1 w+ A& LAt 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:
+ Y. ]& |8 e4 W8 A' H' xWhy Performance Matters
• Productivity – doing more work with less
: B$ {$ T; J! ho Improve end user productivity
o Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
5 p+ E" y0 x% J2 s( `5 U/ d• Reliability
; J( r) ^3 B3 m4 M) Eo A well tuned Teamcenter environment also improves system stability and uptime.
. t; W7 b2 `# a1 vo Less opportunity for data corruption
o Fewer operational errors/problems
• Cost Savings
o Less waiting means less time wasted.
6 T! Q* j: Y7 ?Quick Case Study: Company ‘S’
+ B( W7 H5 l: \# A  ?! }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.
  J) h( B/ K2 s: {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
Common Performance Bottleneck Causes
9 R) B3 N( D% \3 M, l8 K5 FUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
/ E1 Q7 z. x% V# E  y! z2 AOverloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
3 |" L3 H4 r# O! D2 |& b2 WLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
5 j* x- o& `# Z4 Y, ^Databases – 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.
• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
* L( T5 Z; r; q  t: VMitigating Database Server Bottlenecks
, Q4 o& x6 u6 J% G& g7 ?/ q9 L• 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.
• Must have fast dedicated storage for DB files
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
/ ^! p9 ]4 \- s( k2 Po Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
4 w2 a" y  L3 |' @% N8 L1 to Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
* h6 q! n) J* So Use disk controllers with a battery/flash backed cache.
o 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
; F, w, T! j' o$ Ro 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.
• Use a good quality network adapter(s)
7 D( M3 I) F9 I5 s0 Oo Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
# ?9 G  q( _8 ^/ X9 v( V1 w• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
1 w+ r' r' ]. k• Overloaded Tc Servers
• Poor Web Tier Configuration
• Poor FMS Configuration
1 n( I% f) p, v• Debugging Turned ON
/ e! J5 E' B4 W- o5 ^0 N• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
; r1 l0 S" d) K8 y4 H- T2 I! ~• Put Dispatcher modules on separate computers away from other Tc Servers.
; o' ^4 i, L6 s, L: o  L• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
& @5 h$ U* n. S4 b! U. J• Use load balancing for Middle Tier & FMS:
8 m$ |# t1 x3 {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.).
# G6 s5 E$ r3 B' C4 w( Qo Set up multiple FSC cache servers to take load off busy volume servers/storage.
# Q( }# X( O$ DWeb Tier Configuration
• 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.
9 Z3 @/ n: `4 p• Enable http compression if not using WAN acceleration
3 k. t+ Q% I0 G. K/ Go Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
2 h$ k2 @% [1 ~o E.g. timeout values, max # of threads, Java memory, etc.
  d2 ~6 I& l1 F2 l; p4 To Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
0 m3 \$ M( W* ^9 }" M9 o/ P+ a. ho Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
• Data improperly routed
3 D" ]8 w; y7 W1 h0 @4 No 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
7 S4 D- d* Y# `" |o For development purposes only, remember?
' K5 r: s. [8 J7 B• Missing client IP address subnets
4 h- g* ^" c3 }. U7 ^! e, D" R4 w5 C• No load balancing
  B7 _! N# o+ r+ D• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
FMS Configuration
• Ensure routing is correct
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.
0 R1 G+ \1 n9 `/ _* u+ ~8 J3 Oo 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.
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
( Q; e4 n3 f5 B0 T  ~! e3 w• 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.
/ ^# @7 I/ L" l& G' @o Place client maps in the closest FSC group to their location.
• Use multiple FSCs for load balancing
( ^1 @. t1 n. a5 M3 J1 Z4 Z2 T: o( @# n9 Yo Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
* H- H$ l; K: l- u7 Fo Use redundant FSC cache servers to load balance each other. Also provides fail-over.
8 \1 ~, n* k+ t• Place FSC cache servers close to users
& _) T$ l- c5 J5 t0 S  Uo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• 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.
• Prepopulate FSC caches
8 y0 x0 Q; q& `/ q. j. M& Lo Run a nightly script to prepopulate shared data across FSC caches.
% O$ C" \8 d- @2 V7 x3 NMisc Teamcenter Changes
, `) r: f0 o/ {' A• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
2 s7 M" w, k: ]4 x' ko TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
3 N3 {+ s4 {% }! G4 n. Ho 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
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
# M6 R- h8 x, v' t* ?$ _& E6 [4 K  E• 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)
4 W4 E8 a$ d7 d5 P5 f+ {$ i• Optimize OS network settings
! y0 e" M! w7 o0 g  p" no OOTB settings are insufficient
. Y$ w! V  Q, Y% S& x) |) eo Applies to both servers and clients
9 b# U  d9 {$ To Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
! h9 T3 k: Z" ORecommended Server Changes (Windows)
0 W# q9 n' s' }6 Y+ C& gSee Presentation.
0 a  R2 t, n* O4 fRecommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
* x2 O* P2 [% Y; ]+ ^4 Q7 J• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
1 E# r* m+ x- v# X• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
2 u2 \3 X& q* ~+ @% Y• Available at http://www.wireshark.org/
# t$ D" y7 l8 E% x% W5 S  L/ z• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
! c8 e$ h4 X: O; S% D+ E4 O* y• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
: s$ h8 G6 [1 E/ |' Q+ @) ?6 |; Bo Teamcenter Deployment Guide
' u4 j! V: g2 k+ O9 _6 {( Qo Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
, K2 s6 K  `% N0 z) B• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
4 P& Z' b6 u. W! }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
2 j3 r% T* x$ Ko Siemens Blog on Technet
 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
o Teamcenter – Database Performance
6 H; @5 m* B) M1 F( ^/ no JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
/ T- f) B8 [# S2 f5 Ro Teamcenter Database Server Configuration & Tuning
4 B6 @8 a& H" T  M! CContact Information
& k! M4 \4 n. W5 u9 l# ^/ s* SLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
3 A- W2 W6 U* B% \" z- d3 NLinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
) h" Q* \) t$ N4 l8 ^$ R( eAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
, ~$ x7 J/ F2 e1 L
0 a9 F  w4 D5 F0 i% P' {

xiefeixiang

调优厉害啊

a150159

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