|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
( E# w/ l: [7 ^5 Whttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
1 t8 P# g$ ]2 A1 T0 f' T1 t! S- nhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
$ q) i! R) c& {+ }, }; I6 i5 Q& q4 u2 d( _- P9 ]' k
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation% Z+ @ i `; p2 B U* b1 a* @; g
c( C' }/ K5 t6 C |! {/ qLarry Carpenter* d4 g/ x4 j! B2 A
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
$ |- [) w0 {: WFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
1 J% |) q4 @/ t: xWhy Performance Matters
; Y0 W% F+ F5 x3 L {& J) a% B( }• Productivity – doing more work with less
1 U& k2 H+ W7 B8 K" L, F q5 Wo Improve end user productivity# q. ~$ ]6 b0 Q% [. d5 y/ P% W U3 X
o Improves administrator productivity% L5 T( Y2 u" a+ M0 d M) ?
fewer help desk calls responding to or fixing preventable problems
0 D; ]# p$ |9 d W& f• Reliability
! E4 q1 t0 i6 Go A well tuned Teamcenter environment also improves system stability and uptime.8 t4 x1 G* l# q8 v
o Less opportunity for data corruption
* }4 F( E7 Q5 X/ q- Qo Fewer operational errors/problems
3 D5 ~/ [7 D I n$ m• Cost Savings
2 ~1 x( J% T, s: j- do Less waiting means less time wasted./ y' ?" Y' K0 ~8 Q. \9 G
Quick Case Study: Company ‘S’
1 Y2 G; ]3 o$ V& VPerformance 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.
5 k# Z( f; G/ W2 lSee my March 2012 article on PLM World’s website for details:
) t5 L8 z* y: VTeamcenter Performance – Hard-Earned Lessons: http://www.plmworld.org/p/bl/ar/blogaid=152
: {1 G: ^ g" A! L! s/ RCommon Performance Bottleneck Causes
- e0 b+ H8 o' S( s" ^/ a5 J' qUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
; t9 y4 B3 d. ]4 v5 N' m* POverloaded servers — Putting too much on a single server.
* K4 @2 c; x/ z0 I POperating system settings — Network settings most common (e.g. TCP parameters).1 z: y* @' O: b2 E- } ?7 u
Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.& y1 ~8 ?- w8 V5 \3 p: d
Databases – The Most Likely Culprit
- _4 n4 W4 A& p8 o• Database performance is highly sensitive to hardware, software, and DB configuration.: g% ~1 Z5 O3 I7 m% v6 h
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.% _8 R: C1 C% G" S% z
• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
( u* P/ \$ y" k( V2 HMitigating Database Server Bottlenecks
" M! A3 ~. Q/ Z( {1 V• Must use dedicated DB server
& h1 ?" s+ l" E$ L: k Ho Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.: L8 s I6 `) t1 a- n0 m
• Must have fast dedicated storage for DB files
1 m4 r: K$ V& v F2 X( K# }o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
, A5 p+ j- [: I/ D7 ]o Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.# R; P! d/ W/ Y( d; X
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
, j0 ~; b, A1 ro Use disk controllers with a battery/flash backed cache. h9 M9 l! U5 u8 f
o Use multiple disk controllers if possible., @. c, q& n) y5 H* s" e6 Q( h
• Cram the RAM
5 v2 [/ }! M( |* @2 @( Io Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.3 z/ K& e) e9 I5 e/ E: Z
• Use 64-bit OS & DB software' g. \3 I- u) K. L! N/ Y9 f7 \+ R
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 D* K: A( M: V8 x4 q• Use a good quality network adapter(s)
6 U/ j9 P$ w3 x0 yo Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
6 k" c3 m% H* ]# Q" {; c. T• DB maintenance tasks
# J. |+ A- c* {" ~; _3 m No Update statistics and rebuild indexes regularly.
8 J* T$ w" C+ ~Common Teamcenter Server Bottleneck Causes$ r9 G/ S: G$ F) {: l' R# T: _5 S- S' `
• Overloaded Tc Servers
( }& [" V+ l- q6 m+ v! G j• Poor Web Tier Configuration g( l' a7 z& ?( O( w& d
• Poor FMS Configuration
" ^) i8 M. M8 n# O6 s _• Debugging Turned ON
2 P" K7 G$ U; Q& l0 v3 |• Rich Client using OOTB settings) r0 x( K6 @0 M: a6 z! T$ n5 w+ q
‘Unload’ Overloaded Teamcenter Servers
5 w$ v. }" o4 {9 Q( c0 E+ r• Put Dispatcher modules on separate computers away from other Tc Servers.( t/ r5 t% \* Z7 U: s
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
+ _" |4 K; f6 T7 }• Use load balancing for Middle Tier & FMS:2 G! x+ l! K; g
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.).
1 Y& T) T, Z* u, a I( no Set up multiple FSC cache servers to take load off busy volume servers/storage.$ i, h; [; Y5 q: M* N- S
Web Tier Configuration
) {: d5 S- D! v& q8 d• Do not use port 80 or 8080
+ R+ w' U5 D" \/ P) _o 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.
: z$ G6 N8 L0 B d. M( C3 e& w• Enable http compression if not using WAN acceleration a ` K5 X3 l+ u7 v: I
o Must be done on both web server and on clients to take effect.. F: D4 G) k, N7 x9 D) X& A6 a& n
• Change/tune OOTB settings for Web Server/App6 T- H# V* Q4 s, _+ k
o E.g. timeout values, max # of threads, Java memory, etc.
* M/ \4 g; y4 J8 c% R8 Bo Read tuning guides specific to your chosen web server/app
1 K @$ y2 l2 z& r& P3 N• Scale it up or sideways
* F3 ]/ y3 Z! Mo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS)./ p: L" \1 c4 u
Common FMS Bottleneck Causes6 u) n" ~2 m' A! C5 D! R
• Data improperly routed
& }% `" `, ?3 k9 S# A& ko 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.) I8 `, W# Z4 s0 Y( \, D- p
• Using OOTB settings
9 S+ [. c) ?& @* w1 ]9 p5 Bo For development purposes only, remember?
4 \9 m4 `7 M* y/ h7 l; U9 r' R• Missing client IP address subnets& z6 z/ a0 e* p, i# w p1 ?* e% j
• No load balancing
' n6 f& \; u6 Q6 I& M4 R' }• Not using remote cache servers for WAN users
! z0 Z- f; e! }' i! i• Not using remote volume servers for WAN users
3 A; b" S- a' p. U: H7 Q& _8 uFMS Configuration' v& P- }! e- Q* u
• Ensure routing is correct
" W) o/ [0 ]+ s" ?1 q' f, Yo Between multiple FSC groups via entry/exit/link parameters# B7 p: E6 g1 @3 I# J
o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
" p& D9 R1 {7 w2 q+ No Use correct transport algorithms for LAN and WAN users.- } U0 Z8 ^- D4 z
• Tune FSC/FCC cache settings
+ W8 k( y6 H. d5 [( t0 [2 zo Simply picking a total read/write cache size is not enough.8 N) E I+ y% t2 v! V, U
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+ L# X. B/ _% H1 J9 `) ]
• Ensure correct client maps
3 P* d/ A$ X0 `2 s% G' u; ^: h1 h8 A2 Mo Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.0 Q) ]5 m1 w- e: T8 F: s
o Place client maps in the closest FSC group to their location.
) b0 W' X/ l# {' W$ O• Use multiple FSCs for load balancing
! M& i( i, P$ D6 D. Eo Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)+ z z$ s* e% h) t4 D
o Use redundant FSC cache servers to load balance each other. Also provides fail-over.
! L7 h! ` p& y. P% c @. f• Place FSC cache servers close to users
; f+ E# q! o! ^9 X2 ]9 bo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
7 J; \# d# Z7 o- e( g& K! Q x/ q• Place Volume servers close to users
3 p: T. {) h0 f: _ `) ro Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)8 A: n1 k4 i! y+ m( s4 ?: q; @
o Greatly improve write performance (save time) over a WAN especially for CAD data.
8 r0 M+ C" \* s3 H9 v. M• Prepopulate FSC caches
. x0 Z+ T: N( V9 T9 G3 O- v( p) bo Run a nightly script to prepopulate shared data across FSC caches.
" {; B8 ~* h- [( h' K8 {Misc Teamcenter Changes# k9 T6 ]$ t, l9 r0 D
• Disable logging and other debugging tools. Turn them on only when needed. Examples,
7 h: e- R& L0 G, v) N9 Q* ho TC_SECURITY_LOGGING=OFF
3 f0 O5 f: h5 q d) oo TC_APPLICATION_LOGGING=OFF* p) C6 f* w* b3 y; y; P) ^
o TC_SLOW_SQL=-1
4 H9 a8 L* {! }- _' i3 k• Rich Client ‘Teamcenter.ini’ configuration:
* H2 L( R9 _" Q* y, N* _3 n; Go Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).; b0 z) M% x+ S. H- M: [! I
• Enable FCC File Warming
( G. C1 L, D; j: V# A* |" @o Improve startup time by having FCC and Tc files pre-loaded at OS login.
1 t# m: _0 h0 ^2 @* ONetwork Performance
* u4 ~& Q) y# v$ l+ j+ m1 B! J• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
5 Q2 V% v- z; r$ p# y8 x5 Y2 ~o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)# n4 B1 k9 h$ T1 O/ q4 R
• Optimize OS network settings
6 u+ Z, I7 ^; m8 l8 c0 no OOTB settings are insufficient
/ T' Y. d& ^4 ?% q* w/ ^/ h4 oo Applies to both servers and clients
( V0 k* M5 q$ o! T& q' @o Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling, @5 Z6 [* I. T5 |: ]! [7 @
Recommended Server Changes (Windows)
3 Z, c& c% X, E9 N$ E8 fSee Presentation.
$ A$ O* W; q* d# K# }9 Y: SRecommended Client Changes (Windows)
/ q W+ X+ A# N3 i5 N0 b$ d+ b, cSee Presentation.
5 }; T% z" g% VPerformance Monitoring Tools
8 x$ ]1 g5 K5 G' o$ |• Some useful performance monitoring tools:: v! B. t, D, p( z, }; s
• Performance Monitor (comes with Windows)8 C; |7 v) F) [5 Q/ M. M$ e6 ]) M
• Used to monitor OS, Teamcenter, and SQL use of resources: [, o% M8 d; b1 M T6 ~8 F* S
• Wireshark (freeware network packet sniffer)2 g1 Q& l+ D- R, s9 Q
• Used to help identify network TCP performance between computers.* {& V" ~' ?) i6 F7 W+ e
• Available at http://www.wireshark.org/9 r5 o* \6 N w
• Sysinternals Suite (free from Microsoft web site)
8 L8 m# B5 ?# Q" T4 m• http://technet.microsoft.com/en-us/sysinternals/bb842062
. B3 d6 w! Y$ N' J9 p, G+ qReference Materials: }. x/ _! I/ D% { d
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
4 H% p% ]. Q! ~( c+ vo Teamcenter Deployment Guide
! [ Q, a7 s# Go Teamcenter Network Performance Tuning T; W6 t) T- D r3 B+ _" p
o JBoss 4.2.2 Installation & Tuning Guide. b& v7 ?3 L' x& e) m' O! L' V
o Optimizing Teamcenter Client Performance* {( p; f2 r: V* u$ i6 V2 s) D
o Teamcenter System Performance Analysis; K+ Q! q$ N- r1 f! \$ i4 T. x( C
• Oracle documentation & web sites
9 Y1 W7 F* |: S3 }- T) [, o• MS SQL Server documentation in addition to:8 {+ h& D0 C8 U" J
o Best Practices for Running Siemens Teamcenter on SQL Server
; L' b, W) u" ?7 p http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
$ i( v/ W$ l( Po Siemens Blog on Technet
; a$ t0 L4 u0 X J u8 m/ b http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
3 A8 Z# y# e) E5 Uo Siemens-Teamcenter-SQL-Resource-Page
3 W: L9 C6 Y: t6 d ] http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
0 s$ |* w: t& T2 m$ B, {• Past PLM World Conference Presentations available at www.plmworld.org,. R% b9 x- D5 e) l$ o) P i& X
o Teamcenter 4-Tier Deployment – Best Practices( r6 C. I+ S4 D$ c- _! V" a
o Teamcenter – Database Performance$ {& w: b+ F" ~
o JBoss Optimization for Teamcenter& ^" [; i0 [; ~9 u' `+ ^; @; B1 {# f
o Optimizing Teamcenter Client Performance
7 [+ z e! K) o, u8 _1 @7 T( }2 io Teamcenter Database Server Configuration & Tuning8 M% R) X# A4 P: ]
Contact Information- C; T4 O3 [% X4 ^
Larry Carpenter P.E., PLM World Teamcenter SIG Chair, tcua@plmworld.org
$ C0 D+ J: @/ |+ A$ Q0 \4 \Teamcenter UA SIG: http://www.plmworld.org/TC_UA5 b5 K( t# h9 C/ W* ?8 E. H. E
LinkedIn: http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa |1 ~0 E+ W* e; C# h8 g
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com% y: _. N! r2 h6 |
& h3 @. @' _0 v# D0 [0 K |
|
[复制链接]
|小黑屋|手机版|PLM之家-企业数智化转型工业软件学习平台
