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
4 h4 g7 a" H. f+ E3 A8 \9 `( b, n/ _: Zhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

Larry Carpenter
) B- `6 e0 K/ o; c; }5 SAt 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:
Why Performance Matters
• 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
+ c1 g* |) I4 a2 s* Y1 T4 S& r7 Lo A well tuned Teamcenter environment also improves system stability and uptime.
; B1 }6 |+ V, }o Less opportunity for data corruption
( I* A. a! ]& C+ Wo Fewer operational errors/problems
' h; ~5 t( W3 A- g3 c' M• 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.
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
6 v/ {: ?8 v6 v' \Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded 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.
Databases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
5 O" B3 ]' f8 g, |  _4 D' h2 f• 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.
: e6 p0 m; }8 v+ B) G/ cMitigating Database Server Bottlenecks
• 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.
# L3 C5 t: n( c: a+ D% p• Must have fast dedicated storage for DB files
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
- D# f6 d  z$ N5 s7 f2 \8 qo Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
$ o9 W7 [+ k# B8 L( So Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
/ V$ P- P+ G. Qo Use disk controllers with a battery/flash backed cache.
) s8 q# T4 L$ i6 i* Y  [o Use multiple disk controllers if possible.
8 m8 V8 Z7 M$ i& R• Cram the RAM
5 [. [: x5 e$ f1 oo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
. G; z8 O  c$ X/ X. U: N, i• Use 64-bit OS & DB software
) F& S: P' x: |. Y. W2 ^) Po 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.
5 m% B1 z# {8 D; ?/ p0 G& w• Use a good quality network adapter(s)
$ v$ C, ]3 b! }" a. lo Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
/ Q9 E! s1 O' W6 Wo Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
/ k' d' l. V3 N) s+ j• Poor Web Tier Configuration
- y  `& ~5 G% E1 X- L: j; c" M• Poor FMS Configuration
5 g! ~- E) R8 }. K+ t% @• Debugging Turned ON
0 b. W, Z7 `2 q9 T& n3 @• Rich Client using OOTB settings
9 r. m: U/ Z5 z. L2 g‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
9 e" D5 n' ]# N' ~# b• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
4 F$ D) S+ i% m& j, M' n/ b; J, Y  Bo 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.).
9 k- {9 P4 r8 Io Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
6 s" T9 k% a: \) H5 Y) i% `0 x• Do not use port 80 or 8080
2 \3 ~; b5 p7 A/ s5 |; f/ No 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.
( K( F5 X" R; R, V$ M5 [) h• Enable http compression if not using WAN acceleration
! A3 {/ r/ ]7 i& |7 Uo 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.
8 }1 g: E) _0 ?3 ho Read tuning guides specific to your chosen web server/app
& _$ X, }+ i8 H' C1 k+ G  X• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
9 u; K; A' [4 {  @) MCommon FMS Bottleneck Causes
• Data improperly routed
4 o! }3 }% M- X) co 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.
3 [* F  e2 e7 q• Using OOTB settings
3 Y6 C$ l9 C0 e. v( k9 {5 U, |* To For development purposes only, remember?
• Missing client IP address subnets
: u6 \/ u% L8 X, t' H0 _3 P( T• No load balancing
4 ]6 a- K; G/ k& v/ N# ]! Z• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
2 s# H- b" ?5 Q# AFMS Configuration
• Ensure routing is correct
5 P9 N/ ]0 L$ [+ \* Lo 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.
8 I9 C" s: Q& x4 l2 G3 F6 ?8 A5 Po 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
5 N' d3 j1 F3 k/ m$ Z$ a• 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.
! v* G' {0 `' ^/ F9 n/ h  _! b0 D8 Xo Place client maps in the closest FSC group to their location.
, n: O1 l: I  ]* T' }. e0 x• Use multiple FSCs for load balancing
' h7 l- y& v1 l; w% C5 e* Mo 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.
2 n- W1 C2 N( Q: k5 D6 X+ ?' W• Place FSC cache servers close to users
o 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)
' L7 Z7 E1 N2 q5 bo Greatly improve write performance (save time) over a WAN especially for CAD data.
% m; ^1 l( F& C* z4 _1 s• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
( w$ _! w- v" zMisc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
. X. ?0 Y; u! m' Z( R2 p+ \6 Io 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).
; j2 O) n- c( n* S( k• Enable FCC File Warming
0 K  R0 L# O$ i/ o& i" co Improve startup time by having FCC and Tc files pre-loaded at OS login.
3 I2 @6 w: M) YNetwork 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
' {0 u6 ]$ `& a- eo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
9 `7 W2 J, C- r. f6 Z. RRecommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
3 T- ^0 f5 r6 E6 K: s# d• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
3 U3 z/ ]( l& v8 r; T( _% P  P• Wireshark (freeware network packet sniffer)
" y! H2 \/ F6 Q$ J9 A1 Q• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
0 X' w( {0 H& q: O% _- v• Sysinternals Suite (free from Microsoft web site)
• 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
8 I5 D; x1 `1 ?o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
( R/ G9 g, V5 y2 ?5 H: {. ]! `& wo Optimizing Teamcenter Client Performance
( d% a& Z1 g& C& ho Teamcenter System Performance Analysis
• Oracle documentation & web sites
0 U; c' c4 Q3 f6 L• MS SQL Server documentation in addition to:
/ X: j, Y- F0 f- a7 }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
o Siemens Blog on Technet
; s8 z( j: |7 D1 s1 N http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
0 y' l7 p3 H( }+ |3 ?/ G+ eo Siemens-Teamcenter-SQL-Resource-Page
& S4 P. d; ?: ^9 J$ |' ^ 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,
. Z3 I+ k% f& Wo Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
( B' p% H8 Z* G( To JBoss Optimization for Teamcenter
; V* q6 p1 ?1 p0 [3 t9 e0 Yo Optimizing Teamcenter Client Performance
# H; _- u+ K  A8 k% n7 \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
" X2 ^- U* T3 K5 s  dAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
% T8 G5 R& e& W

xiefeixiang

调优厉害啊

a150159

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