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
( W2 D+ C) a* X- Rhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
# I/ w$ t9 a; b6 n9 q
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

Larry Carpenter
% `. u# H. c1 i6 mAt 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
! r/ t# d  j# l* W, sFor 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
: W3 F& _1 ^6 x* s# k* ^' A+ zo Improve end user productivity
3 R3 k3 U1 n4 a2 |6 J% z4 e' S0 t6 }o Improves administrator productivity
3 w3 q8 r5 i( R8 D6 o6 z8 O! m/ Y fewer help desk calls responding to or fixing preventable problems
• Reliability
  b& u' [7 k( x5 D6 Go A well tuned Teamcenter environment also improves system stability and uptime.
5 m9 U' L1 R! t, go Less opportunity for data corruption
7 N7 c" d% c8 i, l2 Q/ c! r' S2 Y3 io Fewer operational errors/problems
& A! o: F, z# q2 [. ^" Y& H• Cost Savings
/ [5 V$ c' J4 N, O* po Less waiting means less time wasted.
& {1 |$ `( ]+ j0 n  I) }5 E( IQuick 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.
; n' ~5 v# t+ W5 LSee 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
( d8 p- }+ y( i7 s# {6 D. O# MCommon Performance Bottleneck Causes
) S2 I- @8 |6 T: L; XUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded servers — Putting too much on a single server.
  K7 K' [" I; T7 D2 q" vOperating system settings — Network settings most common (e.g. TCP parameters).
3 C/ A' q) r4 ?1 fLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
5 e& ^1 L/ j; j" C6 HDatabases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
• 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.
# {9 |- Y9 T3 ?& S! h  [Mitigating Database Server Bottlenecks
• Must use dedicated DB server
0 Q# `. @- E9 B. \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.
• Must have fast dedicated storage for DB files
9 E8 U" s+ n" m0 r9 ^o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
! E9 u' i6 l/ I* mo Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
; R3 S3 s+ ]/ }' D/ t& Uo Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
• Cram the RAM
2 `' @+ F. c' Q# k5 `4 X7 \7 So Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• Use 64-bit OS & DB software
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.
• Use a good quality network adapter(s)
o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
$ P( b( `1 K) {* _5 G/ e" _• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
+ i* o' C$ d2 I' JCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
• Poor Web Tier Configuration
• Poor FMS Configuration
: r( D! q5 [& @* q• Debugging Turned ON
- p' V+ Y( _% r- x9 e+ P• Rich Client using OOTB settings
  p7 q8 R, `4 `  y* H4 q/ D0 t‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
- x. Q: A% `# F$ F8 @• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
7 l1 P  _. {' M• Use load balancing for Middle Tier & FMS:
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.).
o Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
• Do not use port 80 or 8080
8 X8 I- [# ^/ D4 [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.
• Enable http compression if not using WAN acceleration
o 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.
( e7 N! i$ Z  D) n7 S9 do Read tuning guides specific to your chosen web server/app
. }4 I; {. x# _; y• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
5 e3 i+ u) F& n5 {2 f$ BCommon FMS Bottleneck Causes
4 Y8 M7 Y" t- G0 R" y$ R• Data improperly routed
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.
• Using OOTB settings
o For development purposes only, remember?
. ]: \" _/ M. P3 V$ ?' v• Missing client IP address subnets
9 W: M1 U; Q7 p/ i  G• No load balancing
: f; H3 f7 ?0 h) D• Not using remote cache servers for WAN users
! s' v! e" @9 O# r. K& U  L• Not using remote volume servers for WAN users
FMS Configuration
• Ensure routing is correct
o 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.
o Use correct transport algorithms for LAN and WAN users.
1 y6 L/ ]$ W) W, @# t8 [3 s6 p• Tune FSC/FCC cache settings
/ O0 O6 E( k! jo Simply picking a total read/write cache size is not enough.
' V" f( j8 d% r  P- Z# ~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
• 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.
o Place client maps in the closest FSC group to their location.
! e% _. L& j1 {$ s0 U5 T) y8 Y• Use multiple FSCs for load balancing
o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
2 G* @* u4 ?1 ^; g& r- No Use redundant FSC cache servers to load balance each other. Also provides fail-over.
8 p) ^. |+ ^* x. U3 g• 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)
. _- Z. Q, ?# vo Greatly improve write performance (save time) over a WAN especially for CAD data.
• Prepopulate FSC caches
, L( n8 \* d3 G8 m' G" v; A" J' jo Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
# R1 p" m; z6 v* H: s• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
- Z; R7 N* S0 G. _  J+ b! ko TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
/ b! e" T2 Y2 N0 f4 n9 Oo 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).
• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
2 F6 t$ _$ n% O; U7 K, m$ tNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
$ p9 q5 c/ \4 D0 [o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
7 D3 _1 E' p& _) c. U7 v/ u• Optimize OS network settings
2 r0 K9 G) e! c2 Po OOTB settings are insufficient
" H/ p& P; V/ s. g( p/ qo Applies to both servers and clients
! i8 n. P' X7 i6 G+ ko Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
$ M1 b& ]; Q! g3 p5 t' _Recommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
See Presentation.
8 X/ i3 P. G4 r2 e6 ^% qPerformance Monitoring Tools
& ?) l9 r$ w4 L# r1 R, h• Some useful performance monitoring tools:
& f0 N' C; y6 B& O. U" G, V• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
5 d4 C2 d5 P5 k) F! |2 C! @+ _& ~• Used to help identify network TCP performance between computers.
. z9 I4 m- P' x7 t• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
) v6 a% j  h; O: m, vReference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
: w9 h5 p" P# b& Eo Teamcenter Deployment Guide
# _: @( I2 b( r- h4 E8 i4 p6 m# A3 R( yo Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
+ d+ A9 N* P: s# [5 e" r) H8 Po Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
1 D' C. b2 F  @  ?6 ^• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
. j8 Z7 I6 x" D; p2 u( Ro Best Practices for Running Siemens Teamcenter on SQL Server
- w& w; W$ }) V$ _1 q http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
. G! t1 C6 w- Ko Siemens Blog on Technet
2 A6 F# j! w/ I1 R4 L2 ]: V http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
 http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
$ h9 Y  ]: ?# ~+ a# F- r9 {• Past PLM World Conference Presentations available at www.plmworld.org,
" q* G) M  H: Z* \4 M4 qo Teamcenter 4-Tier Deployment – Best Practices
; n9 m  B8 l0 e  p; S+ \( D2 Yo Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
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
. R& o7 y5 Y& ZAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

6 W/ c8 S+ l! v; C- N) V% c

xiefeixiang

调优厉害啊

a150159

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