pivotal crm: optimize your pivotal implementation
Post on 20-Oct-2014
1.158 Views
Preview:
DESCRIPTION
TRANSCRIPT
Pivotal CRM: Optimize your Pivotal ImplementationCesar CenicerosManager, Technical Advisory & Education Services
Agenda• How do I achieve an optimal configuration?
– What resources are needed– How do I know if my system is configured to support my
existing users– What and where to look for performance bottle-necks
• Tools to identify performance degradation points– Database Server Performance– Pivotal Business Server Performance– Pivotal Client Performance– Reviewing and identifying areas of improvement
• Creating a baseline– How to assess changes needed– How to implement changes– Best practices for comparing results
• Q&A Session
2
How do I achieve an optimal configuration?
How do I achieve optimal configuration?
What resources are needed
Tier 1 Tier 2
Business Server
SharePointServer
Tier 3
SyncStream Server
Integration Server
4
Things I have some control
SyncStream Server
Integration Server
How do I achieve optimal configuration?
Typically two things are needed… number one
Tier 1 Tier 2
Business Server
SharePointServer
Tier 3
ResourcesResources
Resources
5
System Design – Architecture & applicationAdministration – Day to day operationMaintenance – Review logs periodicallyTroubleshooting – Research and be accountableUpgrading – Keep up to date
How do I achieve optimal configuration?
Number two
O.S.PivotalSoftware
Third Party Software
Best Practices
6
System Design – Assign appropriate resources to your Pivotal CRM application like having dedicated servers with enough resources
How do I achieve optimal configuration
Examples of Best Practices
Administration – Do not cut corners when managing your Pivotal CRM environment.
UFO &
ACC
7
How do I achieve optimal configuration
Quiz # 1
8
Q.- What are the Pivotal Cache filename extension and where are they stored?
How do I achieve optimal configuration
Quiz # 1
9
Answer .- The extension for the Pivotal client cache files is .RMO and the files are stored in the IE temp fiolder
Maintenance – Be proactive in reviewing your logs, do not wait until your users are complaining about performance issues
How do I achieve optimal configuration?
Examples of Best Practices
Troubleshooting and Upgrading – Try to keep your environment error free and up to date
10
How do I know if my system is properly configured to support my existing users?
Most likely, you’ll know because your Pivotal Users will let you know when and if your system is performing slow
Performance monitor tools can alert you when a Pivotal component is behaving sluggish
11
What and where to look for performance bottle-necks
Pivotal logs should be the first place where to look when troubleshooting non-optimal performance
Event Viewer log can also contain very useful information related to overall performance, not just from the Pivotal side but also from the OS perspective
12
Tools to identify performance degradation points
Tools to identify performance degradation points
Which resources are needed?
Tier 1
14
Tools to identify performance degradation points
Database Server Performance - Tier 1
Database File Structure (.mdf & .ldf)
• The reason the data file and log file are typically recommended to be on separate drives is that when you’re doing inserts/updates/deletes both have to write at the exact same time
So when is it appropriate to put the data and log files on the same drive, and use the leftover drive for something else?
• When the database is rarely updated
• When one drive is dramatically faster than the other drive
• When your application extensively uses the TempDB more than anything else
• When the application does heavier disk activity than your SQL Server (same server)
15
Tools to identify performance degradation points
Database Server Performance - Tier 1
sp_configure: Displays or changes global configuration settings for the current server
This information will allow you to ensure your SQL Server configuration is in line with your business needs and requirements.
• AWE enabled• Max Server Memory• Etc.
Setting Min value Max Value Setting Running Value
Ad Hoc Distributed Queries 0 1 1 1 affinity64 I/O mask -2147483648 2147483647 0 0 affinity64 mask -2147483648 2147483647 0 0 Agent XPs 0 1 1 1 awe enabled 0 1 0 0 blocked process threshold 0 86400 0 0 cost threshold for parallelism 0 32767 5 5 cross db ownership chaining 0 1 0 0 cursor threshold -1 2147483647 -1 -1 Database Mail XPs 0 1 1 1 default full-text language 0 2147483647 1033 1033 default language 0 9999 0 0 default trace enabled 0 1 1 1 fill factor (%) 0 100 0 0 ft crawl bandwidth (max) 0 32767 100 100 ft crawl bandwidth (min) 0 32767 0 0 ft notify bandwidth (max) 0 32767 100 100 ft notify bandwidth (min) 0 32767 0 0 index create memory (KB) 704 2147483647 0 0 in-doubt xact resolution 0 2 0 0 locks 5000 2147483647 0 0 max degree of parallelism 0 64 0 0 max full-text crawl range 0 256 4 4 max server memory (MB) 16 2147483647 38912 38912 max text repl size (B) 0 2147483647 65536 65536 max worker threads 128 32767 0 0 media retention 0 365 0 0 min memory per query (KB) 512 2147483647 1024 1024 min server memory (MB) 0 2147483647 128 128 nested triggers 0 1 1 1 network packet size (B) 512 32767 4096 4096
16
Tools to identify performance degradation points
Database Server Performance - Tier 1
SQL Traces
• SQL Trace is a performance tuning tool, which can be used to fine tune your Pivotal application. It traces the time taken to fetch the data from the database thus having a better understanding on how to reduce the time
The data contained on a SQL trace will help you analyze and possibly identify any long running query, non-optimize searches and even deadlocks within your Pivotal application caused by
• Non-optimized code
• Improper indexing (over-indexing /under-indexing)
• Unnecessary trips to the SQL Server
• Lack of server resources and other server issues (hardware)
17
Tools to identify performance degradation points
Database Server Performance - Tier 1
Database Engine Tuning Advisor
Database Engine Tuning Advisor
Helps you select and create an optimal set of indexes, indexed views, and partitions without requiring an expert understanding of the structure of the database or the internals of Microsoft SQL Server
With this tool you can perform the following optimization tasks:
• Recommend the best mix of indexes for databases by using the query optimizer to analyze queries in a workload
• Analyze the effects of the proposed changes, including index usage, query distribution among tables, and query performance in the workload
• Recommend ways to tune the database for a small set of problem queries
• Etc.
18
Tools to identify performance degradation points
Database Server Performance - Tier 1User data can adversely impact performance depending on various factors, in order to optimize a Pivotal environment it is important to understand the impact that your data is having on the system.
19
Tools to identify performance degradation points
What resources are needed
Tier 2
Business Server
SharePointServer
SyncStream Server
Integration Server
20
Tools to identify performance degradation points
Pivotal Business Server & SharePoint Server Performance - Tier 2
System information (msinfo32.exe).- Displays a comprehensive view of your hardware, system components, and software environment.
With this tool you will be able to get a first look at all the resources allocated to your servers. Be aware of VM environments, for these type of environments the resources allocated can be shared resources.
21
Hardware conflictsI/O Ports, Memory Address
Hardware failure
Tools to identify performance degradation points
Pivotal Business Server & SharePoint Server Performance - Tier 2
Windows Reliability and Performance Monitor is a Microsoft Management Console (MMC) snap-in that combines the functionality of previous stand-alone tools:• Performance Logs and Alerts• Server Performance Advisor• System Monitor.
dllhst3g.exe
nserverc.exe
msync.exe
httpxpt.exe
22
Tools to identify performance degradation points
Pivotal Business Server & SharePoint Server Performance - Tier 2
Server Performance Advisor is a server performance diagnostic tool developed to diagnose root causes of performance problems in a Microsoft Windows Server™ 2003 operating system
23
Tools to identify performance degradation points
What resources are needed
Tier 3
24
Tools to identify performance degradation points
Pivotal Client Performance - Tier 3
Pivotal Diagnostics is a feature used to identify performance issues related to Pivotal Client. This utility allows you to determine which part of your system is causing performance slowdown of Pivotal Client:
25
Tools to identify performance degradation points
Pivotal Client Performance - Tier 3
Event Viewer logs:
26
Tools to identify performance degradation points
Pivotal Client Performance - Tier 3
Pivotal Client log:
..\Documents and Settings\<username>\LocalSettings\Application Data\CDC Software\Smart Client\PivotalClient.<InstanceServerName>\exe
<drive>\Users\Administrator\AppData\Roaming\CDC Software\Smart Client\PivotalClient.PerMachine\CMS6
Levels of Verbosity:1) ERROR: Least verbose2) WARN3) INFO4) DEBUG: Most verbose
Change: In the IafConfig.xml file, locate, and replace the logging level in the code <level value="WARN" /> with the logging level of your choice, for example:
<level value="INFO" />.
By default in the IafConfig.xml, the logging level is set to WARN.
27
Tools to identify performance degradation points
Pivotal Client Performance - Tier 3
Office Integration log:
..\Documents and Settings\<username>\ CDC Software
For Windows Vista and Windows 7 operating systems:
..\users\<username>\CDC Software
Levels of Verbosity:1) ERROR: Least verbose2) WARN3) INFO4) DEBUG: Most verbose
Change: In the IafConfig.xml file, locate, and replace the logging level in the code <level value="WARN" /> with the logging level of your choice, for example:
<level value="INFO" />.
By default in the IafConfig.xml, the logging level is set to WARN.
28
Tools to identify performance degradation points
Pivotal Client Performance - Tier 3
Additional logs:
IafTrace.log Logs the interaction between Pivotal Client and the remote Smart Updater service (an ASP.NET v4.0 Web Service Extension)
SmartLauncher.log Logs issues while connecting and downloading from the deployment server.
29
Tools to identify performance degradation points
Reference resources available on ePartner / eService
If you do not have an eService / ePartner ID, please make sure you follow up with me
30
Tools to identify performance degradation points
Installed Programs
Make sure you have detailed information regarding the versions of all the software that you have currently installed (including service pack, hot fix and patches)
31
Tools to identify performance degradation points
Who? What? When? Why?
• Who is using the system?
• What for?
• When during the day, week month?
• Why do they need access for?
32
Tools to identify performance degradation points
Business Module – Best Practices
Several Pivotal Toolkit tools and commands are available that would help you identify possible areas of opportunity where performance can be enhanced:
An Invalid ID is an element ID which has lost its link to its referenced element.
Duplicates: Objects of the same type must have unique names within their domain
An orphaned database record is one that links, through a many-to-one relationship, to another record in the database that has been deleted since the link was established
33
Creating a baseline
Identifying areas of improvement
Ok, you have gathered all the information about areas where your Pivotal implementation can be improved…
Now what?
35
Create your baseline
How to assess changes needed
36
CPU
NetworkUtilization
Memory(RAM)
Disk I/O
IISResponse
Time
HTTPRequests
How to implement changes
There no specific order or best practices rule on how to implement any of the changes needed.
DB Changes
Optimize forms
Software Upgrades
Load Balancing
Purge Orphans
Hardware Resources
Add indexes
Optimize forms
DB Changes
Purge Orphans
Add indexes
Vs.
Vs.Vs.
37
Best practices for comparing results
Implement Changes (1)Collect Performance DataAnalyze Results
Implement Changes (2)Collect Performance Data….
38
It is important to identify what changes are expected
QUESTIONS?
THANK YOU
Cesar CenicerosManager, Technical Advisory & Education Services
top related