|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
×
http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf 0 i7 o. q: B% T4 N& _! z ^
http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
6 t3 ]+ [ d9 ^( n+ uhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf9 t4 c/ D7 k4 t7 m1 ?3 [6 C7 Y
6 ]! u1 n$ C4 m8 A( g8 p* \: v( CTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
- l2 c( S1 ?1 y( E( v ' v) l4 U4 ^4 X. J, [2 i
Larry Carpenter
3 B8 J# p4 h' r ?4 {' vAt 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: l! c$ I$ f* N2 O) b
For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:! x1 j5 a3 J& n& n c. |
Why Performance Matters1 _* b' G$ q* _2 ?
• Productivity – doing more work with less7 W2 B4 d2 s; Y- l7 W+ m4 u3 i4 F
o Improve end user productivity
8 f0 U7 q5 C* k6 vo Improves administrator productivity
: G/ C0 T) ?" {" ? fewer help desk calls responding to or fixing preventable problems
8 J9 P, ^* Z4 s$ c! n) j• Reliability% k! c) p0 Q7 M$ C, u5 C s( A$ y. O
o A well tuned Teamcenter environment also improves system stability and uptime.
6 e5 ?( r! p5 r+ G4 vo Less opportunity for data corruption
" M$ m; x. A; q( W& o. r) Wo Fewer operational errors/problems
2 t& w0 j) D/ J& @ W% P• Cost Savings
2 C. B7 g( |8 e8 H c9 X" q8 ~o Less waiting means less time wasted.# \, t. B* X4 } @) `4 Y( }8 M
Quick Case Study: Company ‘S’
1 h5 u8 v; ^, ^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.
6 m1 E+ r) W0 y( x% o& {0 ?See my March 2012 article on PLM World’s website for details:9 ?7 n! X- A, Z( Q1 Z6 v
Teamcenter Performance – Hard-Earned Lessons: http://www.plmworld.org/p/bl/ar/blogaid=152& D. o# F; p% x* w- u& G1 M% P
Common Performance Bottleneck Causes! E5 H: @" v. L9 F) L( ]7 I3 ~
Using OOTB settings — OOTB settings are intended for development environments; not production environments., J0 y( `* F: K) |4 }8 \) s& u& C
Overloaded servers — Putting too much on a single server.
% L; C: j$ r: V' h% JOperating system settings — Network settings most common (e.g. TCP parameters).
/ E; N& b5 p: l/ V: d+ k$ e3 xLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
: O K3 K1 F, U0 \Databases – The Most Likely Culprit# X: n# ]& }4 l5 v" y( d: v* y
• Database performance is highly sensitive to hardware, software, and DB configuration.+ j( T |! h' {' J1 w& s; A* c/ _ N
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
K+ d6 Y3 T, W+ |% W/ }• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
( T- f* r0 R' E7 w% l- h! Y+ @Mitigating Database Server Bottlenecks4 w. O: E% r- a8 ]% t8 g9 @
• Must use dedicated DB server% {% ]# d" g# I: ]( l% I
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.1 M4 O! P4 x- l) J6 p/ K- z, R/ u
• Must have fast dedicated storage for DB files8 F+ W; M1 A' c& c* c; I
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.9 V, Y! x5 K8 q' I: [ y% J
o Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
! L. m' M3 p/ F8 V* n: Wo Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations./ s( E( n5 t! B8 l( a& S7 q
o Use disk controllers with a battery/flash backed cache.
3 T9 l# D0 A1 q" \2 I6 Co Use multiple disk controllers if possible.
/ C/ j( Y1 @$ r1 g% A• Cram the RAM
7 G/ w+ o, I4 J- U* x _o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
; t1 U) V7 f8 ?) O: Y) z) v• Use 64-bit OS & DB software( v& O# b& j9 }- G
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.
$ ]2 z2 Q! u' S5 A9 ]: `% {& j! K+ t• Use a good quality network adapter(s)( [$ Y! d) q6 u: h6 ?
o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
* N; l K# [. _6 F" x2 _- P• DB maintenance tasks4 M: g! U2 E; ^2 d0 A
o Update statistics and rebuild indexes regularly.
: e! R5 g u& [ I: s- S, ECommon Teamcenter Server Bottleneck Causes
. Q0 ?! J5 _7 t• Overloaded Tc Servers$ V1 n0 U3 A9 u8 N1 i" v; T
• Poor Web Tier Configuration& }( q4 }7 T2 i4 O
• Poor FMS Configuration. }+ g' e0 C2 W6 z( ?; f
• Debugging Turned ON
' C" \0 J0 r! X- `" I• Rich Client using OOTB settings# r- ?0 e; {$ m; T: u
‘Unload’ Overloaded Teamcenter Servers. t+ p) m# I* [
• Put Dispatcher modules on separate computers away from other Tc Servers.' `4 p) Z/ I3 K$ d } L- ~
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
, f2 e4 Z+ O* x9 n8 ]• Use load balancing for Middle Tier & FMS:- O6 h' ]1 u2 i1 S6 e$ j! M# L
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.).
. t: |& ^5 {5 E0 No Set up multiple FSC cache servers to take load off busy volume servers/storage.- j7 `1 Z6 c+ J4 \3 y+ s( \
Web Tier Configuration
% v2 Z% C3 J$ c- t" J• Do not use port 80 or 8080
0 r& l6 Z3 s( h- c& |- uo 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.
& F5 K# q. {( V0 c) i• Enable http compression if not using WAN acceleration+ X) V! _0 J& T! P
o Must be done on both web server and on clients to take effect.9 A* q9 O. L1 K
• Change/tune OOTB settings for Web Server/App
. K! z. r5 x4 ?! J5 r! H3 N5 io E.g. timeout values, max # of threads, Java memory, etc.& L4 ] U9 g2 E+ L/ ^$ T) ]5 P
o Read tuning guides specific to your chosen web server/app
5 T: x! A( n: B3 r' U% p$ Q' M• Scale it up or sideways
: V( t$ Q2 T+ |& Fo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
6 k5 W7 U' q& V, R6 @1 mCommon FMS Bottleneck Causes
$ z' G+ w2 B6 ?• Data improperly routed" V' V' J& U3 ^+ \; E
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.
0 F, ~$ M! H: U3 \1 k& m$ x7 S- q• Using OOTB settings
* d* Q4 N! j% u5 M# zo For development purposes only, remember?& E% E4 r9 D) e4 l3 I# [
• Missing client IP address subnets
$ a* A+ U3 v4 b0 D- v1 F* R; J6 o6 J• No load balancing# h1 |$ j0 J; b! \2 g" F, t
• Not using remote cache servers for WAN users6 y5 U0 Q6 [7 ~
• Not using remote volume servers for WAN users
4 t0 n: d9 n% vFMS Configuration
( N0 J& ]4 _6 O0 g• Ensure routing is correct
4 w4 J I# F G3 x, Io Between multiple FSC groups via entry/exit/link parameters
% H0 y8 O6 a2 }o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.( f/ d1 ?2 x2 y" F- i& m1 g
o Use correct transport algorithms for LAN and WAN users.
/ ~/ z3 G- h% b: V" J8 E• Tune FSC/FCC cache settings/ \" h5 D; z9 u- h2 k: o8 A
o Simply picking a total read/write cache size is not enough.
) e0 h: _- s7 Uo 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
1 v) d* [7 P( _9 N9 N• Ensure correct client maps: T4 Z4 \* B6 L$ f# z
o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.! {# Q( V' g* ^" J$ B
o Place client maps in the closest FSC group to their location.9 |/ g1 \% t4 w; F* Y- {# K8 i. i
• Use multiple FSCs for load balancing% A* s' A+ _; Q0 \( H& V$ j7 r
o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing); T& e w/ T& {4 Y$ u$ ]# L
o Use redundant FSC cache servers to load balance each other. Also provides fail-over.6 @" d+ y8 I* S: n# O
• Place FSC cache servers close to users5 q9 {( g+ e; ]; B8 i
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
+ c# M ~8 b) _) t% r2 p• Place Volume servers close to users
: I8 T3 R" Q( k# L+ c1 Ko Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)0 U8 C! _$ R% l- h9 G
o Greatly improve write performance (save time) over a WAN especially for CAD data.
6 W' @; x) \8 ?! s& W- s• Prepopulate FSC caches3 y, c6 @& y3 z8 b# t9 e
o Run a nightly script to prepopulate shared data across FSC caches.
; s; \ c- G0 u" E5 XMisc Teamcenter Changes8 M/ Z9 y7 I% |, ]
• Disable logging and other debugging tools. Turn them on only when needed. Examples,
$ b- t6 }( F3 N% k5 Q+ Ao TC_SECURITY_LOGGING=OFF
6 P/ p# c D5 H4 Y0 _# }3 ao TC_APPLICATION_LOGGING=OFF
3 ]8 K U) a% K |. f/ _/ p0 Qo TC_SLOW_SQL=-1
0 b- O. M8 G8 U: V( i9 ?6 s) d• Rich Client ‘Teamcenter.ini’ configuration:1 M+ F* s' j" n* |3 [! 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).3 P8 W0 C) @, U" i% G
• Enable FCC File Warming( V% @5 p$ \) Y% w# p
o Improve startup time by having FCC and Tc files pre-loaded at OS login.5 T5 l2 p/ M) ^; m9 o
Network Performance
! t' c/ t& x3 F3 ^! @! y# C/ _) J• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
, D" i3 c: o: Mo If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)9 u4 ^, r8 t0 m& `( E' [( I0 W
• Optimize OS network settings
9 Q8 t+ Q# E) [# a# k# Oo OOTB settings are insufficient
h) s/ W) b+ {2 G8 {o Applies to both servers and clients
Q. ^& y+ d4 p+ R8 B1 Bo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling* |6 W% q) Q' q' l- u) I( x
Recommended Server Changes (Windows)
H2 A q, D# P- f1 _See Presentation.
7 D8 H. {; V1 k* c* uRecommended Client Changes (Windows)8 }* a$ z- {- L& ~7 l! I' K+ w7 P; `
See Presentation.& Y D( ^8 p$ [: T, x0 t! g
Performance Monitoring Tools
5 A9 w2 X& o3 d7 d• Some useful performance monitoring tools:
9 J# {" l7 R5 `7 e2 |0 X) G4 D• Performance Monitor (comes with Windows)
, ~" G* U, m4 l" f3 o• Used to monitor OS, Teamcenter, and SQL use of resources
; s/ E- y% d: |4 Y# A3 {• Wireshark (freeware network packet sniffer)
: y' H5 e* a n$ K/ j# n• Used to help identify network TCP performance between computers.
1 \/ P, K1 a P: ^0 r• Available at http://www.wireshark.org/
6 C9 Q& r9 w$ L( Y2 W$ y' `* ]: M g4 j• Sysinternals Suite (free from Microsoft web site)
* {5 [4 u- X. y9 w$ J• http://technet.microsoft.com/en-us/sysinternals/bb842062
8 x' C0 f p% @, rReference Materials
3 z, b( @7 g9 L; s5 o. ~• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/+ B& r1 [4 n" a9 g" I3 E& s2 G) h% N
o Teamcenter Deployment Guide
! j2 h: f% ]9 P# d- r3 R+ Qo Teamcenter Network Performance Tuning- D2 m* u( o4 E" k% |- ^. p
o JBoss 4.2.2 Installation & Tuning Guide
9 e3 J; |( |9 co Optimizing Teamcenter Client Performance' ?: A6 W, F* v6 f6 r$ }
o Teamcenter System Performance Analysis+ f- M- c( {: \( r- E
• Oracle documentation & web sites0 O% b; n# B ^4 M6 ]
• MS SQL Server documentation in addition to:
7 q4 O) R+ Q1 e4 R3 D4 Y) b9 wo Best Practices for Running Siemens Teamcenter on SQL Server
" x& F6 i# m: X' J2 b1 g% p! C: K http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf# L5 h) z) u) E2 Q! D
o Siemens Blog on Technet
% |9 [0 Y! s6 w* q7 |& F http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
/ o8 U0 ~/ D% b! s% r/ ^o Siemens-Teamcenter-SQL-Resource-Page# J" J: `4 T! {; y
http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
% P8 f& `. b9 D) }5 X• Past PLM World Conference Presentations available at www.plmworld.org,+ s, K9 | ?! P0 ]# u+ t
o Teamcenter 4-Tier Deployment – Best Practices8 p4 n" m; ? m& C0 i
o Teamcenter – Database Performance4 j1 Y- [6 \. Y1 l% l
o JBoss Optimization for Teamcenter' @+ X' ?1 a" @7 ?$ l' b
o Optimizing Teamcenter Client Performance
& U$ `6 d& R0 p m( v2 Ro Teamcenter Database Server Configuration & Tuning
9 b9 M: ^ Y3 u- f. M5 nContact Information
9 j( j. a; W2 eLarry Carpenter P.E., PLM World Teamcenter SIG Chair, tcua@plmworld.org- y/ W* s5 P: L2 y# X5 B
Teamcenter UA SIG: http://www.plmworld.org/TC_UA) p: X0 G$ t0 _8 S" j
LinkedIn: http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
/ U9 q! n9 u. M7 F# t3 _Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com- I# H5 Y2 J" @ A/ n
) w# b, C# F1 V. s
|
|
发表于 2017-5-12 16:17:54
发表于 2018-1-10 16:28:46
