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
* d- {1 p. F8 dhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
7 j4 ^7 f% R! B# y* R6 {
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
1 I+ g. s. F6 X. G3 b/ F; s/ R; r
Larry Carpenter
) Z& r* Z+ a( x& x6 ?- K0 e# @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
) [. O; Z, D% C  m! ]8 {' VFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
Why Performance Matters
& q2 D; L* R" `6 E• Productivity – doing more work with less
o Improve end user productivity
o Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
6 g. b$ j2 d6 @5 Mo A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
: `9 \: k! z2 W$ }5 R' `8 D+ H• Cost Savings
o Less waiting means less time wasted.
% N9 G% m# F# a. NQuick Case Study: Company ‘S’
. F& X  x% z0 |! r  FPerformance 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
9 @7 N: n% o/ Q- qCommon Performance Bottleneck Causes
* A, R+ j& B; K* D; ~0 fUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
4 V% N$ z1 C& i# h! h3 O3 `. BOverloaded servers — Putting too much on a single server.
% F* z1 ]; [  ?7 [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.
Databases – The Most Likely Culprit
- m7 n3 A* v  ^1 ?• Database performance is highly sensitive to hardware, software, and DB configuration.
2 V* O+ f) V" N' W- Z; b, D• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
) Z( i: I! [( f9 ~3 C• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating Database Server Bottlenecks
0 g; l/ I8 }* v/ H  _• Must use dedicated DB server
+ c/ N2 Y% v" v- J* Ao Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
4 I: \( d9 ^9 n! t• 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.
: K+ f+ \3 ~6 N$ C/ To Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
" v7 x& G0 S9 Bo Use disk controllers with a battery/flash backed cache.
  h2 ]7 {+ H+ @0 o" Do 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
9 D0 T5 M) V6 z" l2 b+ 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)
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.
: c/ Y* ~. e+ J, O7 ]4 E: p, I, dCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
, ?6 J& g3 Z  e% b, ~8 d• Poor Web Tier Configuration
$ r+ f& t5 h  ~! S( ]' X8 p• Poor FMS Configuration
3 P. x! D. e0 o. ?, C• Debugging Turned ON
) |; ^# Q; R2 {' w• Rich Client using OOTB settings
7 E$ E9 k' R' g; G$ j/ h* E‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
& Z9 Q  L( B: p• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
) Q) W/ }9 _: m  c9 Do 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.).
: A9 k% P* m) c6 ]* p% q3 ]o Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web 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.
• 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
o E.g. timeout values, max # of threads, Java memory, etc.
- |; r9 E8 J" c5 j: v: eo Read tuning guides specific to your chosen web server/app
• 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
3 V/ g' r' d: v7 x• 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
6 c0 C$ Q! u* J6 ?3 O* ]o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
0 I2 Y3 m+ r& k5 v5 V* J3 L• Not using remote cache servers for WAN users
+ C5 h, W5 @% P5 D' l4 ]• Not using remote volume servers for WAN users
+ b$ g3 n! E6 I9 B$ ]; I% {FMS Configuration
. z" X, s# M* U• Ensure routing is correct
o Between multiple FSC groups via entry/exit/link parameters
! G3 g1 Q% M' _9 F, Io Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
7 R4 q/ b& ]  j9 x# E9 Ro Use correct transport algorithms for LAN and WAN users.
+ k" f% s: ]- u" M) ~• Tune FSC/FCC cache settings
" [. ?: R+ g0 o9 y3 K! Z4 L. ho Simply picking a total read/write cache size is not enough.
! j2 U' X& |7 V" mo 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
% H1 E: x. `/ O. [# ^  g7 [• 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.
+ J; D% h; r7 ]5 {, d5 {/ f9 Uo 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)
; m, J6 R% H4 Z! W/ w& E% no Use redundant FSC cache servers to load balance each other. Also provides fail-over.
8 V& @! r4 j# M• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
, `  I/ P; Z+ o; L• 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.
) Y4 c$ V( T- V& s• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
  c" g8 _) F% P. N4 `/ ?Misc 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
7 s* K& Y6 c6 F% F* ~o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
6 e* o& y/ Z( Y8 n3 W1 W2 q" Lo Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
' N, G/ Q, n5 e! N* i) a5 P# I• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
/ c6 K" I% q4 \5 l/ t0 NNetwork Performance
1 F- j* V  ^4 P9 M$ 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)
" O) b# }6 v! y0 S( h; U9 {! K• Optimize OS network settings
o OOTB settings are insufficient
o Applies to both servers and clients
- ?( D- P9 X# j# X1 j, h0 qo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
Recommended Server Changes (Windows)
See Presentation.
# v1 T, {+ B: g, B7 WRecommended Client Changes (Windows)
% U# u- q5 p( r: ^* l0 c+ \See Presentation.
Performance Monitoring Tools
6 L- x  R& u8 F' A9 y7 H• Some useful performance monitoring tools:
/ Z1 I' E- T) p( G  H• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
0 I! O! \# u( a4 b• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
1 C' I7 v" ~' V1 O1 w" W• Available at http://www.wireshark.org/
) T- _7 f/ a1 f6 c6 _• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
8 x4 e( B* G0 iReference Materials
7 P* @; r+ U  J. R( l8 X! t6 e• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
; W; R4 x4 |2 E0 c) No Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
9 `* s$ Q( Z2 Wo Optimizing Teamcenter Client Performance
+ A) g" @: N1 g. Y1 C6 j' ?o Teamcenter System Performance Analysis
• Oracle documentation & web sites
% m/ t3 K- ?6 r  ]4 S2 \• MS SQL Server documentation in addition to:
0 ~# U* o' J& Z0 p9 w. m  w0 K; Io Best Practices for Running Siemens Teamcenter on SQL Server
# i* Y; A9 A/ w' `) l% l http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
7 ]" k& L6 l( t# Ao Siemens Blog on Technet
+ F& |0 r; [! P+ F. f5 }2 O+ k 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
  Y+ O3 {- a- s- r( j  ^* h• Past PLM World Conference Presentations available at www.plmworld.org,
" u, }$ Q' y: k% io Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
# q5 ?1 N' g! z& X5 co JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
: W! g# }) W3 A0 m9 S8 Z, YLarry 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
7 ?1 Y$ V' a& M1 X1 J, _! @, }Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
# O8 w2 M8 ]+ h' U; O

xiefeixiang

调优厉害啊

a150159

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