|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
×
http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
; c' g1 T& i' c& `& o7 U* G' s6 [& [http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
/ @& n" w" @4 x, V8 Z# ?6 Rhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
/ K0 G+ S$ l. P0 ^- _2 \$ ~4 o c
% b! q5 ] {! d8 |2 H$ X- H; U7 ~Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation: f$ {6 j% m( X# `0 H. n8 o, B% \ T
8 t* m0 Z5 \* ]# P5 M4 x+ K* F4 wLarry Carpenter
" @' U1 R1 p: EAt 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
7 C' g: }5 b. j. [For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:1 W. W. r3 c. q1 D' g7 O; T% ?
Why Performance Matters
% Q9 Q" Q8 R# J" j/ M8 d• Productivity – doing more work with less! c/ Y4 s- N$ S5 `
o Improve end user productivity* M$ f" m# a: k
o Improves administrator productivity; D$ I9 d, y4 M
fewer help desk calls responding to or fixing preventable problems( k+ l) s Q" L& e9 o5 G; L
• Reliability5 a7 X0 i$ Q! `. N! I& L7 X
o A well tuned Teamcenter environment also improves system stability and uptime.
6 z, l2 H9 p. g8 m( Co Less opportunity for data corruption+ `) K$ V6 v+ M( B
o Fewer operational errors/problems8 o0 b! S( A, g T3 t8 H0 P
• Cost Savings
+ k C4 ~6 |$ j0 g$ w, i; Ao Less waiting means less time wasted." O) J" i4 W. V: H' ]( ?
Quick Case Study: Company ‘S’
$ m. f! t) G) v; e1 k# s4 n0 rPerformance 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.
& u" n% z, ^, [* q4 k# JSee my March 2012 article on PLM World’s website for details:
3 H! o; i K) DTeamcenter Performance – Hard-Earned Lessons: http://www.plmworld.org/p/bl/ar/blogaid=152
8 F% Q! Q; `7 V" A8 f5 Q# N# W/ mCommon Performance Bottleneck Causes
% j6 k. y J- I$ y* s3 jUsing OOTB settings — OOTB settings are intended for development environments; not production environments.9 @7 o. ?# k: @1 q3 S) K b% I
Overloaded servers — Putting too much on a single server.
( j; n3 V. r0 [7 @% UOperating system settings — Network settings most common (e.g. TCP parameters).: l; D. [/ m6 G( H7 Z6 t# X
Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
' U5 q3 q( ^0 f) s VDatabases – The Most Likely Culprit
; A* @7 f$ L. s+ \( @+ b/ H• Database performance is highly sensitive to hardware, software, and DB configuration.. b" X G2 ~* S% D! N
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.3 {4 u, E% ^) {, t( B' N
• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
! e$ D$ r+ w. x u eMitigating Database Server Bottlenecks. u9 W* Z5 S* H' M9 _
• Must use dedicated DB server
% v* M; ]! }" X' Zo Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
; y' @3 k, c7 u# H, W5 E8 c7 g5 R• Must have fast dedicated storage for DB files9 w% T# z, x* R
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
( t, d+ w1 z5 Q8 s4 z, Y; P7 x5 V& l% yo Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.6 V- j/ B; g& Q) I
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
, R# Y; a7 h% T K% J' q4 \o Use disk controllers with a battery/flash backed cache.4 \" [' m5 e7 T/ y+ U$ R
o Use multiple disk controllers if possible.: U* l3 A& E. B3 F8 \- [5 p; |( C
• Cram the RAM
$ q5 o" Z* @' { @1 y" Fo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
2 D$ K3 v* }* \; M• Use 64-bit OS & DB software
3 T4 U: ^; v+ Y- S8 \o 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.
$ Q8 z$ _/ w, T! s1 b2 h- j• Use a good quality network adapter(s)
$ ^9 \" j. G, ?1 Y p" P3 S3 No Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.5 I% I* h6 ?# ?) q& R- P
• DB maintenance tasks8 L6 u6 b& q" e# v0 P
o Update statistics and rebuild indexes regularly.
|# o4 I$ H% D& hCommon Teamcenter Server Bottleneck Causes
/ b- A' r( [! R2 Q# n! ~( V• Overloaded Tc Servers
& ]. z2 q/ i, p3 D7 V. D3 d• Poor Web Tier Configuration
9 D. M) O0 w* {% j9 y• Poor FMS Configuration# V' v9 x) h- p& V) x1 A1 _
• Debugging Turned ON
% F% @: Q# L* A( [% j0 E8 H8 z• Rich Client using OOTB settings
( N3 k: N# }! `" M" N6 @‘Unload’ Overloaded Teamcenter Servers
% N$ e& }8 Q2 d• Put Dispatcher modules on separate computers away from other Tc Servers./ r( d p9 h& q4 p
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.7 O; i2 ?' _3 m& @- M
• Use load balancing for Middle Tier & FMS:$ f' B$ }# C9 m8 j
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.).
# J% o' M$ s. e# `- ?0 \2 |o Set up multiple FSC cache servers to take load off busy volume servers/storage.
* V- u; W! N: m% Z) FWeb Tier Configuration
: D$ O6 Y: X- o3 |+ d+ d" V% ^• Do not use port 80 or 8080
/ [9 c0 w8 v) L! K) `9 F* zo 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.
, ^4 J3 l1 z% e& p# v% I! `• Enable http compression if not using WAN acceleration
0 w; @" L8 [5 r R. C+ S) Do Must be done on both web server and on clients to take effect.. q# n# T( b4 o9 V/ C# g
• Change/tune OOTB settings for Web Server/App
; j/ i: a ^$ s7 y2 Z. f6 C: U' jo E.g. timeout values, max # of threads, Java memory, etc.' ?& n$ R: F" c8 T4 t- s
o Read tuning guides specific to your chosen web server/app/ y$ K( g! V5 j5 ]* j) b
• Scale it up or sideways
, U& d9 Q% @; @& K( a4 zo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
4 a3 M: N8 x4 H; W9 t$ a2 QCommon FMS Bottleneck Causes
0 _4 R+ B7 y& j9 j• Data improperly routed
7 o' U- {8 g( a9 I/ ho 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 l. h! S2 \& u( q
• Using OOTB settings
7 T$ F& M' @9 K) Q5 ko For development purposes only, remember?* ] C) n( {1 D9 ?8 j
• Missing client IP address subnets
. x' N0 _& f8 ~" u0 V* [. T5 ]• No load balancing
# n6 f% g% g% {9 B v! T# f• Not using remote cache servers for WAN users. b9 }3 a4 R) u( k: D! [& N H
• Not using remote volume servers for WAN users
! C. x* o3 {2 |- @0 QFMS Configuration
" _) K' T4 E0 b6 t. p1 `+ [4 ]• Ensure routing is correct/ d6 c6 s( ^ v/ f3 k; |3 f/ `- }
o Between multiple FSC groups via entry/exit/link parameters i# B; a! Q; k1 R) `( m8 v9 L- {
o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.4 Q1 Y# ^3 M# m$ R2 [
o Use correct transport algorithms for LAN and WAN users.( J& R7 i2 R7 Z9 s) l8 G
• Tune FSC/FCC cache settings
?/ j& @. d7 S8 Z7 W4 O8 `o Simply picking a total read/write cache size is not enough.
9 N# n! x" R" }8 No 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
8 c4 n) P: v1 H7 n4 V• Ensure correct client maps( {. G9 B- K: W% B' _, e
o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.5 y# G+ Q4 Z9 e
o Place client maps in the closest FSC group to their location.3 |: p" j5 x! D
• Use multiple FSCs for load balancing
6 W' L- ~1 S; F6 Vo Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
H9 M; [ M- W5 o' U1 U1 b/ j; zo Use redundant FSC cache servers to load balance each other. Also provides fail-over.5 x8 w0 A( v- H7 @
• Place FSC cache servers close to users+ X7 R' t% e( P& t; X, Q6 `0 \
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
# Z8 y; ?2 z9 p0 z- i• Place Volume servers close to users9 A& v5 ]* t5 a
o Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)8 J- U7 p7 l' W6 N9 L
o Greatly improve write performance (save time) over a WAN especially for CAD data.0 H& k1 V+ u9 h8 X6 m+ K
• Prepopulate FSC caches- C# {+ z2 _' b- b
o Run a nightly script to prepopulate shared data across FSC caches.8 W8 }1 W$ _$ K1 n
Misc Teamcenter Changes) j! |* a# z; y! T4 X
• Disable logging and other debugging tools. Turn them on only when needed. Examples,6 \) A& @2 ~; ?7 Y/ c0 l
o TC_SECURITY_LOGGING=OFF- s- Y+ k+ v4 F2 k, K, S
o TC_APPLICATION_LOGGING=OFF
1 e7 j3 T2 S5 a1 l1 Zo TC_SLOW_SQL=-1
* }, n# [% H: p G• Rich Client ‘Teamcenter.ini’ configuration:3 L- X! V' g8 t! O: Y
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).
- |: D9 V/ _0 Z; o6 J• Enable FCC File Warming' ~8 `* i4 G& N' a# j
o Improve startup time by having FCC and Tc files pre-loaded at OS login.$ P& O& O7 q6 d/ W: n' H! G
Network Performance
* w+ W; x, R& g; ~% Z; }• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
: d. g, u5 }1 b ?o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)/ L; V; C! ]4 e( [% }
• Optimize OS network settings" V9 f: H' e" O$ a. _( m
o OOTB settings are insufficient
" ?3 d' \" K0 a! i8 S) fo Applies to both servers and clients
( i6 S$ d+ b- E$ J# \/ {o Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling3 b: J& m4 }3 f( z4 z) E- \0 b
Recommended Server Changes (Windows)
9 s; j2 b5 T- ?3 l* MSee Presentation.; j, ~: L T/ ~% Q5 u' n- i
Recommended Client Changes (Windows)
" ^9 f9 H0 `0 v6 c7 N. S/ USee Presentation.1 _. h6 b" x Z% ~0 L8 B( i2 x9 E
Performance Monitoring Tools
+ |# F* e# [" {9 r. l4 [1 V• Some useful performance monitoring tools:
0 p8 E- Z2 X: V$ g# Z• Performance Monitor (comes with Windows)
' @6 Z0 Z/ J) _6 a4 T• Used to monitor OS, Teamcenter, and SQL use of resources1 G8 m+ _% h: H8 }/ I' E; p! w) V- g
• Wireshark (freeware network packet sniffer)8 S& B" a# Z# U
• Used to help identify network TCP performance between computers.4 J6 W+ O9 A, i3 F0 J: }3 W- o
• Available at http://www.wireshark.org/; ~7 x3 j4 \- G
• Sysinternals Suite (free from Microsoft web site)& j) }5 H0 u& y4 K
• http://technet.microsoft.com/en-us/sysinternals/bb842062
' k) t1 ~2 x' @ U ~7 m) T1 ~' i uReference Materials
; ?/ a( |1 a' T, a• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
b# `( H" h8 a: s# @4 _. M- S/ x8 Lo Teamcenter Deployment Guide, E+ j% Z$ @7 `* t1 C* E
o Teamcenter Network Performance Tuning
& B' e9 n" H: x( b( Z, z$ Zo JBoss 4.2.2 Installation & Tuning Guide
! ^) t% ~5 \$ O# q7 p j4 Vo Optimizing Teamcenter Client Performance5 _7 l* `3 z( J# ^
o Teamcenter System Performance Analysis+ j( p) U' O1 i) t2 d( m- r' [
• Oracle documentation & web sites; D. Z" g$ {5 A% @
• MS SQL Server documentation in addition to:$ ^) Z h* ~7 x/ n! G6 I
o Best Practices for Running Siemens Teamcenter on SQL Server
* R, B/ k+ X! J5 }( W http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
6 G% Z$ x7 d- Q3 P* eo Siemens Blog on Technet
) ]3 J( M' f1 A0 ?& N; Q9 K: Y http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/' f5 u& h) n! i$ [0 K+ B
o Siemens-Teamcenter-SQL-Resource-Page6 ^( {2 x( k" E; s" L2 z! c7 A- H B0 j
http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
- _7 u% z2 z( j' p- Q1 n/ _• Past PLM World Conference Presentations available at www.plmworld.org,
' k& N2 F S/ |5 [2 Co Teamcenter 4-Tier Deployment – Best Practices
5 S2 u9 y, |- V, K0 X2 g; w. io Teamcenter – Database Performance
% S* F8 j- n% s, A, Q* S5 ~o JBoss Optimization for Teamcenter
0 l; V, N- {! n) d: E8 Jo Optimizing Teamcenter Client Performance- S3 ]$ r0 s" q! X
o Teamcenter Database Server Configuration & Tuning1 W! B S c+ G& O6 j
Contact Information+ r& ~3 e6 z9 f. w+ B" r
Larry Carpenter P.E., PLM World Teamcenter SIG Chair, tcua@plmworld.org) K: _$ }% ~. }9 F6 u7 X5 a
Teamcenter UA SIG: http://www.plmworld.org/TC_UA
) A* T( z2 s/ G$ w, VLinkedIn: http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
1 `8 G" u$ ^0 M5 U# `; V+ N2 qAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
5 O6 G8 h4 k1 ~7 G6 m
* E/ ?: {$ G! S J0 U2 d7 v6 p |
|
发表于 2017-5-12 16:17:54
发表于 2018-1-10 16:28:46
