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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
& R8 z1 z. u0 {9 ~2 E% ihttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

) V$ \" C; A' h; W5 u/ a1 ~/ vTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
) R6 |9 r) w* b4 V1 v5 D
Larry 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
For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
3 P1 |! B# R; k: u% U" QWhy Performance Matters
+ L/ W  {& Z3 i/ n7 P* ^• Productivity – doing more work with less
+ Q7 U/ s* w0 N$ L* d8 u- uo Improve end user productivity
o Improves administrator productivity
  Y5 @# e  I- Z' ]: a fewer help desk calls responding to or fixing preventable problems
  \* e/ Z" C6 D• Reliability
- `9 Y  k. q; ~* p: _" Qo A well tuned Teamcenter environment also improves system stability and uptime.
  Z$ K  w$ _7 Z" z$ I% @o Less opportunity for data corruption
o Fewer operational errors/problems
  f) ^% J5 y, m+ r/ U* ]3 X• Cost Savings
( k! r3 u: P- {+ z6 A4 Ao 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:
) W: V; u9 |9 q! ETeamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
1 O# R1 t& ^5 x- _; U9 ?Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
$ }; t9 i3 I+ q, Z: [8 Q% \4 u- POverloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
+ b+ q* ^) I3 b7 tLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
, w# k* v- h; D2 g- D+ }Databases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
0 h, K( \  k$ x- B! Y$ u0 Q• 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
• Must use dedicated DB server
  L- T# a$ j3 q4 b! }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.
$ n" q& W8 _. c3 A8 Z3 L• Must have fast dedicated storage for DB files
7 {  l2 |9 k( P' X- o- T( }; zo Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
1 O0 \* q, }3 o5 O5 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.
- n( z6 K( |& o1 {5 g$ D% Xo Use multiple disk controllers if possible.
• Cram the RAM
2 h5 d% ~9 S8 N% y4 m; d" |! To Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
" J) M/ ^! I- J+ t" Y• Use 64-bit OS & DB software
9 _- [- j) G7 F$ S2 ^6 `8 Do 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.
* m, \* x' u/ T2 `8 R/ D: I3 x• Use a good quality network adapter(s)
' {' R6 F/ v7 L& R) q7 yo Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
4 R2 c7 Q1 M" q' W! X1 }o Update statistics and rebuild indexes regularly.
% L- ?7 R1 l1 P1 @3 zCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
• Poor Web Tier Configuration
- k0 L, ]9 t9 J, V6 d* o; g2 V• Poor FMS Configuration
: n: h# U/ j5 y6 F% @( n• Debugging Turned ON
8 b+ y7 A9 m1 a• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
: ]9 {8 a# v% _, f% |- x# g0 w• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
" N0 i. T4 V! t( m• Use load balancing for Middle Tier & FMS:
1 \. u( g& t7 y4 ^2 d$ h( z6 I; ao 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.
Web Tier Configuration
• Do not use port 80 or 8080
+ m6 O" j3 G. I3 D' ho 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
3 u3 {8 P* a) d  }0 e4 W& @o Must be done on both web server and on clients to take effect.
) d# H* ^7 I' a8 j; J' N• Change/tune OOTB settings for Web Server/App
# R3 X; v$ F5 |( _o E.g. timeout values, max # of threads, Java memory, etc.
# x0 {7 e) L; u0 to 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).
" `+ e5 `( I) ~8 RCommon FMS Bottleneck Causes
. t& d* A1 c1 v5 W7 }. x1 w• 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?
• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
* {% M7 S7 S3 c# v+ ?+ v• 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.
7 Z) I2 }- ~, so Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
1 m9 K2 z3 g! Y! k$ w) s/ yo 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
3 O3 S9 e- M2 |, S% E• 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.
$ B# J; D  ?& L- Z, }. e0 ?* n. U• Use multiple FSCs for load balancing
9 H7 P; [, s* Xo 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.
, I+ Z! a9 I) D, p/ ]/ O/ j. D8 i# h• Place FSC cache servers close to users
+ U2 w* w" P5 e1 Wo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
$ f/ A* c/ i% ]0 }: V+ mo 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
o Run a nightly script to prepopulate shared data across FSC caches.
, n- U; M: j1 D' nMisc Teamcenter Changes
4 i# [4 S5 P/ ]: Y9 V3 {7 ^3 U• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
4 t) w1 n! f  q' t' ]o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
1 j7 ]" W$ s1 W* p: l( C) io 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
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
) |: D8 n% p; k0 h9 v  ENetwork Performance
( `9 s, l0 e( e( b5 Y" @+ K, _9 i2 s: m• 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
" v/ [1 D1 o, Wo OOTB settings are insufficient
o Applies to both servers and clients
( ^- G& H. R: V5 Go Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
. [  I: |+ i) X+ v  z) gRecommended Server Changes (Windows)
; }2 `; N) L9 F/ mSee Presentation.
% S' t" O/ y# d( GRecommended Client Changes (Windows)
' a4 ]* O  ?3 L2 v8 l* qSee Presentation.
5 h/ ?: `0 W  a; L- OPerformance Monitoring Tools
• Some useful performance monitoring tools:
• 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/
3 T* c' {$ Y1 |' J• Sysinternals Suite (free from Microsoft web site)
2 j9 O% f4 D' x' S, z• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
4 W5 q$ {# n/ R; A% ao Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
4 i3 O8 L1 {; \, G$ d1 t- R& jo JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
: w9 M# T& J/ B# L% g6 E/ go Teamcenter System Performance Analysis
% N4 r$ G6 i1 W8 U1 G3 G• Oracle documentation & web sites
, m% H9 j, a$ }/ u9 K• MS SQL Server documentation in addition to:
5 p/ n3 m" L: g$ M- Qo 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
& D: d5 c2 w/ ^o Siemens Blog on Technet
  y2 ]1 `. B. \8 v! B3 z 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,
5 H; x6 j+ q5 ~/ H/ @" ~o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
+ T, a* A8 H& r! ?" K' Xo Teamcenter Database Server Configuration & Tuning
4 A" V3 m. M+ G/ g0 LContact Information
( T5 i" ?# K" }Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
, i5 ]- Q9 v$ t) Z" iLinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

) W- \* L" r% d. y

xiefeixiang

调优厉害啊

a150159

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