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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
0 r  t0 A0 j# {, b. o/ a, z4 a: ehttp://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

2 n; e2 U# v" w" t9 g* KLarry 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
. e& c. h! l4 {0 S  @/ a; o; TFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
# {9 f" b# q8 P  c* j4 F0 uWhy Performance Matters
• Productivity – doing more work with less
/ N( m! C9 J) f. `! [3 [3 |. vo Improve end user productivity
o Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
/ ?; P+ ?4 U9 O  Go A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
* ]6 o  s0 v' G8 y2 T6 oo Fewer operational errors/problems
• Cost Savings
* G% O3 v3 ?6 [2 a& po Less waiting means less time wasted.
Quick Case Study: Company ‘S’
# Z. n. [4 ]) [9 ~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.
$ c( L2 u7 T% N) DSee my March 2012 article on PLM World’s website for details:
/ r8 `4 ^% C0 q. BTeamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
: F0 i5 x4 G) u: ?9 XOverloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
  I; z8 J- u& H" }& ?' yLack 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
% z! n6 k3 L, S  x9 [! ?• 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.
Mitigating Database Server Bottlenecks
1 n0 {/ C, B' \/ M; G• Must use dedicated DB server
# |. d, ~( Q# C) s( Jo 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.
2 W4 W/ c+ `# G0 J4 h- O( Co Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
0 N' ~- J0 W. X1 s9 Ko Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
' m6 s1 k1 ~4 ~* O1 N/ uo Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
4 _+ _6 ]+ ?' o• Cram the RAM
" C( s9 s0 J7 k7 Lo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
8 ^( r; D9 ?" F• Use 64-bit OS & DB software
$ t3 q: |; n# C8 z' o3 w" lo 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
6 K8 a. [7 n/ d7 \8 w' v: ^o Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
• Poor Web Tier Configuration
• Poor FMS Configuration
• Debugging Turned ON
• Rich Client using OOTB settings
2 c) P6 J3 b" [" [‘Unload’ Overloaded Teamcenter Servers
. R1 ~% l# K( z3 B: s+ z• Put Dispatcher modules on separate computers away from other Tc Servers.
, t( O( m1 O9 ~5 K4 i4 \• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
9 Y% r# B1 h6 o# \3 `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.
  q( K2 w! u4 R' Z5 ^2 N+ T# W2 H2 vWeb Tier Configuration
8 D3 X1 k. B8 t" G- V- b' I• Do not use port 80 or 8080
$ e: W, O6 d0 S% H: D* `3 Fo 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
/ O4 M6 X. X; e- k" F, `1 Z& oo 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.
o 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
• 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
3 o" y5 l0 ?: S" }$ U6 Qo For development purposes only, remember?
+ Y! C$ C$ ~/ H$ f2 }• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
6 {1 l# I9 A# f$ N+ Y2 D2 h1 yFMS Configuration
• Ensure routing is correct
- s/ n- T# g' v1 t& P3 E8 zo Between multiple FSC groups via entry/exit/link parameters
3 J7 j5 e# K( |: _( }- J# q+ V5 [, t+ ko Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
9 O) E- K0 X3 u% ^7 Uo 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.
/ m" R* ]$ U& E; ]4 S9 F! k: @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
9 ]' T" h5 X: o, \# b• 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
o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
4 ]/ L; C& L) x7 x6 V7 ^o Use redundant FSC cache servers to load balance each other. Also provides fail-over.
• Place FSC cache servers close to users
+ c) ^+ v4 b5 b& T: qo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
1 ~& s: U: J  N  w8 @3 g! [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
& z2 E7 l$ Y2 |' ?5 j2 x+ Po 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,
, w$ Y3 v! z3 f* `o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
2 h+ V1 H8 e# \8 @$ F" ^o TC_SLOW_SQL=-1
6 P4 E$ O/ E. s* K. o• 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).
* e% d5 ?3 Y: q6 b• Enable FCC File Warming
$ s4 x: i# t1 K% K" c  N" [o Improve startup time by having FCC and Tc files pre-loaded at OS login.
4 V- ~. Y6 ~$ d; a" s7 W! eNetwork Performance
• 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)
• Optimize OS network settings
o OOTB settings are insufficient
o 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
Recommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
See Presentation.
+ d7 p6 w) ~  I! W, D- Y! DPerformance Monitoring Tools
  ?& T( ]: b, B3 {8 }• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
+ q, S5 W) i; ~! n; Q• Used to monitor OS, Teamcenter, and SQL use of resources
8 o' ^, v+ Q/ C( G- P• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
- b5 z7 |/ N6 U+ T• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
  S9 C% c& f8 X5 IReference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
7 Q" W# F: v/ F8 ?/ U% po Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
7 Q% T" C% P. \$ O0 F+ Y* o* {o JBoss 4.2.2 Installation & Tuning Guide
" }/ Q" o/ x7 j6 R. `& `' U: Xo Optimizing Teamcenter Client Performance
! L1 _3 i4 S0 l6 A% L# C; Uo Teamcenter System Performance Analysis
• Oracle documentation & web sites
• 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 D9 ~+ i, }8 Mo Siemens Blog on Technet
' G0 z& {& _! [4 l6 l6 G http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
1 x# F, d: V9 L/ n  o, ^o Siemens-Teamcenter-SQL-Resource-Page
 http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
/ X+ u- g# s* w. h) L• Past PLM World Conference Presentations available at www.plmworld.org,
3 P/ z* f5 M5 k% N0 ]o Teamcenter 4-Tier Deployment – Best Practices
: j0 V6 g" e8 `; {7 ?9 E/ Lo Teamcenter – Database Performance
- T. h0 K/ E: B" ?o JBoss Optimization for Teamcenter
. i% o& |' j8 qo Optimizing Teamcenter Client Performance
; r) l* n" g' S  p, S3 Bo Teamcenter Database Server Configuration & Tuning
' J4 S- n  {- c, Z" S. \Contact Information
0 p7 H0 @% l% V4 h7 ?8 fLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
9 F! G) q, I: I. ALinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
8 H) V# y  n; _$ l' NAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

xiefeixiang

调优厉害啊

a150159

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