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
" U0 c3 _) f3 u5 M" a1 i" ihttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
7 P. {+ c; i3 Z* D6 J% S
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
( I+ Q1 l6 z7 z3 l: W! H" W  R
, [( J( _1 v/ o* Z3 f& d, a, BLarry Carpenter
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
For 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
0 L8 V# {5 Y8 P' t0 O' Wo Improve end user productivity
; |6 U) `& ~3 @2 S1 yo Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
3 P: c% u* e% e* w) `• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
7 v& g, N" r+ L7 E$ xPerformance 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.
1 i: n4 S. n3 A7 f. b( H1 d- q! \See 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
6 x% }& f' R5 \, E% {7 T" yCommon Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
: @# `- W, g5 VLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
5 f' m' `$ w* }) Q8 f* KDatabases – The Most Likely Culprit
7 W. A, Q5 A5 v& K' G& x• Database performance is highly sensitive to hardware, software, and DB configuration.
3 w0 |' m' u7 i/ O: I- j• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
" ~. `" ^, v- S) u4 F3 K) s• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating Database Server Bottlenecks
) P; e& D3 N: ^, p• Must use dedicated DB server
1 A# G6 C6 \* G  Q3 A- Fo 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
! T$ T! O6 \2 I, J; {+ q2 ro Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
% o9 f( c* `8 m- M% Lo Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
6 u' k8 ]. V9 [4 |. o4 ~4 Go Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
) z, F, p% v. E* L8 ao Use disk controllers with a battery/flash backed cache.
# v, s+ O: M: F3 e: |0 so Use multiple disk controllers if possible.
• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• Use 64-bit OS & DB software
, W/ O- A' @- oo 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 M) P4 E' `' K8 I5 ?8 h• Use a good quality network adapter(s)
4 f) a( O( O$ z; e. ]6 y* `o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
+ `* J6 Y% x+ p3 f' A# B• DB maintenance tasks
2 x- O3 o( j3 B8 C7 ~( B6 ]o Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
" `( S) P# N" V• Overloaded Tc Servers
: W6 l; T" Q4 w' q' G; v6 J/ R& t4 t• Poor Web Tier Configuration
• Poor FMS Configuration
8 c9 G. }( k5 I• Debugging Turned ON
& W2 V7 d8 }' A9 b0 ~2 z6 q- N: n• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
  o! f9 u' D  D9 I' D3 z• Put Dispatcher modules on separate computers away from other Tc Servers.
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
5 t4 ~& ?  N: T( |  q8 D6 w. w• Use load balancing for Middle Tier & FMS:
- i: T9 E% a$ ko 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
% C3 l! P" I$ T• Do not use port 80 or 8080
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.
4 k8 \3 u- G% {6 N* ^• Enable http compression if not using WAN acceleration
2 ?. u' D, D+ o0 J* \" ro Must be done on both web server and on clients to take effect.
( M  u1 h/ h# c2 _; v* E• Change/tune OOTB settings for Web Server/App
4 c, Q+ S, i; So E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
( x3 B1 d' {* e) U& m% s& Q9 zCommon FMS Bottleneck Causes
& r" ^- x  v1 \# C• Data improperly routed
: z2 `+ I. I9 l' Mo 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?
  h# X' @. m% W% [• Missing client IP address subnets
! _: Y+ M+ h2 o6 f• No load balancing
( v' P' p$ f7 U, }/ e• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
FMS Configuration
• Ensure routing is correct
& r2 q- j5 L5 G! J/ ~# d# To 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.
) U3 X0 m- T7 J& ko Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
) p+ x+ E& ?7 ko 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
3 G1 o$ u4 {! h. w• Ensure correct client maps
5 \6 A/ s' ?; @o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
. H1 ?. {4 u6 {' eo Place client maps in the closest FSC group to their location.
• 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)
o Use redundant FSC cache servers to load balance each other. Also provides fail-over.
• 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
+ n, _% _. \( U, [7 V0 B) xo Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
0 d, \7 I- R' W! n. h, Ao Greatly improve write performance (save time) over a WAN especially for CAD data.
• Prepopulate FSC caches
: `3 @0 M8 L0 x+ M" E# k/ v$ n4 _; Zo Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
5 K5 s" p% A2 W0 q4 E/ e& Q• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
: j% V8 b, ~( }1 Oo TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
; J. p4 b4 e; }, F# R• 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
& A' g7 z7 U1 f, oo Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
1 ~6 P: _6 s: D2 f; s3 po If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
* z- ]( \2 r: K! K• Optimize OS network settings
o OOTB settings are insufficient
o Applies to both servers and clients
# e# G' N) w/ W4 Y* eo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
Recommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
! z) }9 k7 J8 R/ T• Performance Monitor (comes with Windows)
0 q8 U- A  \; q• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
$ O, u' P. y0 y& [# p" T: z& E• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
; v0 |) \/ u' t0 J: No Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
8 L) m" s/ [+ N3 |o Optimizing Teamcenter Client Performance
" e* Q$ }* e* O  \% eo Teamcenter System Performance Analysis
• Oracle documentation & web sites
5 O% J7 o9 h2 w7 ]/ H• MS SQL Server documentation in addition to:
; }/ a  _+ ~0 h# do Best Practices for Running Siemens Teamcenter on SQL Server
 http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
o Siemens Blog on Technet
 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
• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
: }8 k  c! K, P7 q3 `$ lo Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
& j  y" H. E) F* w$ QTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
/ }8 q! t9 Y$ h7 \% XLinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

, C( H! F' E$ n0 j2 C

xiefeixiang

调优厉害啊

a150159

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