|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
4 U }# m+ _' q6 F: d4 j- uhttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218 : ~- v7 F8 w+ A/ }4 q' z6 S
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf: k4 ?" X) H! {
2 |4 Y6 z8 A9 D9 N0 A
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation* R+ C7 Y D' |' j6 b* l
, a: r6 u* m0 c# K4 h4 G% [
Larry Carpenter6 G# w" [7 V# i* A8 ]: s2 P( q
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: b0 F0 m( x7 V
For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
3 L/ T; ] B6 ^. F" O3 ?' G! oWhy Performance Matters
* k4 m* s; T" f• Productivity – doing more work with less
$ J5 o% e* P- C5 x8 @2 F n6 `o Improve end user productivity1 B, }/ g3 v0 G1 @3 s
o Improves administrator productivity
/ p0 N" G$ p" h( _: g fewer help desk calls responding to or fixing preventable problems2 h* c( R6 }! k& l; _5 @1 m
• Reliability4 S& w6 ]( a N' T
o A well tuned Teamcenter environment also improves system stability and uptime.
- Q5 l& V/ H9 U6 t- Oo Less opportunity for data corruption
+ ~1 k* U% A# L2 Po Fewer operational errors/problems2 |/ @8 b" d4 @3 ~7 B% d) F
• Cost Savings+ h. U) |- D' J/ h" d9 w1 C
o Less waiting means less time wasted.- w! b; J' z2 @' Z% _$ |5 k6 O8 y
Quick Case Study: Company ‘S’/ T2 z ?. q+ j, w4 Z0 W. ?
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.
# y8 m/ S$ f) G. J- f& v. eSee my March 2012 article on PLM World’s website for details:3 Z5 r6 }: `: F6 K! S' _/ Z5 ^7 V& [6 [
Teamcenter Performance – Hard-Earned Lessons: http://www.plmworld.org/p/bl/ar/blogaid=152
4 H: p" r* Y- R2 h2 Z6 j6 v, H+ l' @Common Performance Bottleneck Causes
, t" w+ c* @3 D4 b4 m, q' JUsing OOTB settings — OOTB settings are intended for development environments; not production environments. O! ~1 T6 C* r/ @8 \" h6 N
Overloaded servers — Putting too much on a single server.' _, B2 [/ B% x+ ?: q! i
Operating system settings — Network settings most common (e.g. TCP parameters)./ T d7 |6 u: \9 u$ y& d. d6 l
Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.# L0 z1 F# N/ T) c! B" o$ i& T
Databases – The Most Likely Culprit4 k- F8 }4 Z/ ?( e( O
• Database performance is highly sensitive to hardware, software, and DB configuration.- E, }( @; f' T0 i2 S( v! A3 K
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.' U" J* P( a- y
• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.* S7 s; X' N0 T3 x; }
Mitigating Database Server Bottlenecks
; L! e0 e# r, c; p4 ]# k3 W6 n1 W• Must use dedicated DB server
7 ]5 X9 K2 \# Wo Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.6 C9 {- A' r; ]0 B2 ^* _% N# X
• Must have fast dedicated storage for DB files3 P! E5 x' A9 G1 {3 K
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
3 B' F Z# F* {% D" e! no Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.; Q4 U% l) z& e
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
, \0 L) b8 u1 z7 Po Use disk controllers with a battery/flash backed cache.% J% F- v2 j/ L+ Q& A
o Use multiple disk controllers if possible.. j! t8 K# p2 U" T: G
• Cram the RAM9 g& c; P+ A, |5 A+ E
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
6 I( C: t$ X! h4 a/ n) E/ R• Use 64-bit OS & DB software X4 p$ K* Y4 A9 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.6 R) X( }( y$ s! N4 }3 M, H* J7 e
• Use a good quality network adapter(s)
6 a( _- |; L+ `& q, ]9 }o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
& M8 E* J4 v* u• DB maintenance tasks
4 A; W, Y& t; A' h! Bo Update statistics and rebuild indexes regularly.
0 c, r8 P) d6 Y' n, yCommon Teamcenter Server Bottleneck Causes+ Z! c7 N/ c9 o9 L: E
• Overloaded Tc Servers
( ?' \3 I7 I- }% V+ J3 V( r3 w D" e! j• Poor Web Tier Configuration
0 a+ G2 F0 u2 O• Poor FMS Configuration
4 N- d5 N; ]+ Y7 _• Debugging Turned ON
& H( S% t! K" P0 g: F• Rich Client using OOTB settings" w: h4 ?/ [9 T
‘Unload’ Overloaded Teamcenter Servers7 V+ [; t7 M6 z
• Put Dispatcher modules on separate computers away from other Tc Servers., P+ K5 ~$ F5 q
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
5 _3 C0 k4 I% g: j• Use load balancing for Middle Tier & FMS:6 j# x `4 M/ q( W4 @2 Z7 b# ?
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.).- {7 Z. ^% V7 ?2 e @
o Set up multiple FSC cache servers to take load off busy volume servers/storage.% }9 N2 W) Z2 w
Web Tier Configuration
$ N3 N! `* D1 e. I" e0 z• Do not use port 80 or 8080
) b ~4 K- s* \' m: q( J. Z% fo 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 M) m' S5 t5 m/ m k: U$ m0 a* G
• Enable http compression if not using WAN acceleration
* @0 w+ ^! p0 V; _o Must be done on both web server and on clients to take effect." c$ |8 L0 g/ A; N: w& a
• Change/tune OOTB settings for Web Server/App1 ~* f8 P: {3 O8 {
o E.g. timeout values, max # of threads, Java memory, etc.
; X: p! c7 r! \% t! E$ O; ~5 |- qo Read tuning guides specific to your chosen web server/app/ n7 N0 c: u# e0 p. _9 V+ f
• Scale it up or sideways
1 J& C! n: L) A2 S3 E; I+ O5 To Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).* }% u. W7 A; z: b; R( b$ Y$ y) @
Common FMS Bottleneck Causes i; [0 k( h5 S r& q, K
• Data improperly routed
& }1 p- b: g+ x% Q( T: B5 F# Uo 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.' D/ z' N, z% U) ?) y
• Using OOTB settings5 m: B) V! y* G5 e5 t- U) I3 e8 U( t
o For development purposes only, remember?
% r N7 K4 K6 |- c+ a3 _( @• Missing client IP address subnets1 y: l1 }; N) O4 c
• No load balancing- S, `% W) l4 P9 w1 p+ R7 W1 Q& c2 G
• Not using remote cache servers for WAN users$ E) T! b+ k, Q0 m
• Not using remote volume servers for WAN users
' H3 L* ~' _0 CFMS Configuration: o. ^, v0 T3 O- w; M
• Ensure routing is correct
& e, X, J8 R. ^5 a8 S% |5 Fo Between multiple FSC groups via entry/exit/link parameters
; z8 i g; b3 B0 {$ Yo Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
3 ]9 r- h& T. _" E5 do Use correct transport algorithms for LAN and WAN users.
) d/ c \: E+ |+ n• Tune FSC/FCC cache settings
, {$ P9 |( _6 {5 uo Simply picking a total read/write cache size is not enough.* x; B2 t# W2 d/ M% T
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
: N) t, }( V! |8 F7 ?• Ensure correct client maps0 T- S7 ]) Y# [( ~+ S0 V8 l
o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
6 k9 C( Q5 R5 w. f+ q5 `" K( do Place client maps in the closest FSC group to their location.
$ n6 k) Y7 [' Z1 B• Use multiple FSCs for load balancing+ e3 U' K( s% a" S
o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
1 E$ ]$ o" y, q! C! R# ~6 lo Use redundant FSC cache servers to load balance each other. Also provides fail-over.4 k# M8 `1 N5 ^
• Place FSC cache servers close to users
3 P7 l3 U1 q8 Q [% j( z3 E7 Ko Greatly improves read performance (load time) over a WAN for groups consuming shared data.
8 c2 e/ ]& v7 {! q6 d4 \• Place Volume servers close to users
5 B( l, `4 }* ~1 ?' z9 Go Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
l6 |9 Y9 K, d0 X; I4 \6 t4 Z- `8 ^o Greatly improve write performance (save time) over a WAN especially for CAD data.- `: e( b1 C0 e4 R2 M7 f. _
• Prepopulate FSC caches/ m8 F+ C' w6 j. u$ j6 m' |
o Run a nightly script to prepopulate shared data across FSC caches.% P6 ]# E& p! W4 w* w6 D2 D( z
Misc Teamcenter Changes6 C7 Z) S) X' {# {$ G, C. f. a
• Disable logging and other debugging tools. Turn them on only when needed. Examples,1 B3 S5 Y, p; Q5 t. p4 Q1 X
o TC_SECURITY_LOGGING=OFF
: I$ }4 F+ R) z: _9 }3 [o TC_APPLICATION_LOGGING=OFF
: K5 l; r; E, oo TC_SLOW_SQL=-1
; Q( e- y4 h6 b+ I& n0 j) F( `! ^• Rich Client ‘Teamcenter.ini’ configuration:6 G x$ {) v2 T6 y' c
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).
: T" F! s$ o' h! X& x$ @• Enable FCC File Warming. A7 T/ g/ W, t
o Improve startup time by having FCC and Tc files pre-loaded at OS login.& E8 q0 P9 ^7 S. P8 X7 S
Network Performance% q( H- A# M- Y+ U2 ?
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
1 x; i- f- n9 i P# Y/ Ho If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
4 ~& k+ C; |5 I8 D `/ E• Optimize OS network settings) p% J0 N: ^0 L
o OOTB settings are insufficient
( s$ _1 d" S% C) E" ro Applies to both servers and clients
- u) p$ g+ b6 ?) j4 Q/ d1 no Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
/ }( j0 V. k+ p6 t7 BRecommended Server Changes (Windows)' z0 a. j; Z& h0 H
See Presentation.
& s1 L' {4 I. HRecommended Client Changes (Windows)
3 j0 U, f8 o. q5 ^1 P- YSee Presentation.
) e# K, P& M7 i# CPerformance Monitoring Tools0 F& s7 V2 W, G, q4 t X( J& t
• Some useful performance monitoring tools:9 p( F1 u4 U6 h$ _! z5 i
• Performance Monitor (comes with Windows)" q: R' x; c+ I# S
• Used to monitor OS, Teamcenter, and SQL use of resources
- X% q, _0 {2 \# q$ O• Wireshark (freeware network packet sniffer)
" b7 ~" N" _8 q- a# s• Used to help identify network TCP performance between computers.
1 F P$ f3 {# |7 @* ?* a: I5 ?3 D• Available at http://www.wireshark.org/# k9 {( O- |. t1 ~6 C2 x. p8 b
• Sysinternals Suite (free from Microsoft web site)
" p, D$ X: |2 l( d4 J. V; X• http://technet.microsoft.com/en-us/sysinternals/bb842062
1 F' Z7 @( n; G# H l0 ^/ I1 iReference Materials
; \0 ~0 M" W7 A5 i0 r+ {% g• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
1 s! y s, ` H6 f* Xo Teamcenter Deployment Guide/ |. c& a- `+ ?5 F* z
o Teamcenter Network Performance Tuning
% m. u* g& y4 n, ] ?9 c C+ \( C/ ]o JBoss 4.2.2 Installation & Tuning Guide
+ G" { G7 W0 d* Ro Optimizing Teamcenter Client Performance
/ \$ [5 N% B; ?3 C/ \; ^ t% Po Teamcenter System Performance Analysis' m3 }! w5 R; M( T, E. V( t' Q
• Oracle documentation & web sites
. @5 m9 `8 U r6 ]: c• MS SQL Server documentation in addition to:
6 O# t7 ^1 K* n C/ }o Best Practices for Running Siemens Teamcenter on SQL Server9 V/ j. [3 ~ [. ~8 ~9 B' W
http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
2 s4 t$ R: a3 h5 v" q q5 |o Siemens Blog on Technet5 v( G# [7 u& c0 C, o+ [: ^; {
http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
0 W/ D* ?' y: H5 N8 Q& Qo Siemens-Teamcenter-SQL-Resource-Page
F+ u4 R8 T/ X! S4 P http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
- @. j. f9 w# v7 s1 N/ k& ^& H• Past PLM World Conference Presentations available at www.plmworld.org,. h- @1 N' ]5 r. G
o Teamcenter 4-Tier Deployment – Best Practices
L- J& i& g7 M6 l: O2 Co Teamcenter – Database Performance
/ o/ {4 h! r5 x9 J0 to JBoss Optimization for Teamcenter
( }7 Z0 z% I5 ]" S n" [5 M0 A. no Optimizing Teamcenter Client Performance
" W- X! j5 R- G6 |' M K/ k3 no Teamcenter Database Server Configuration & Tuning4 X- Y* Y. l G) J3 H
Contact Information. k# q# b( E9 f. u3 W) L
Larry Carpenter P.E., PLM World Teamcenter SIG Chair, tcua@plmworld.org
! h- ? D/ s& S7 R( |/ r9 {) p' y- dTeamcenter UA SIG: http://www.plmworld.org/TC_UA
: p! Y: ~% i9 W# HLinkedIn: http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa5 n/ B4 m3 V( E! a+ ?+ p
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
# j) r2 `3 y, e# g! @, C& z* U5 ]5 k8 Y2 a# T! b+ Y. r
|
|
[复制链接]
|小黑屋|手机版|PLM之家-专注工业软件生态建设，大模型CAD创新生态
