创建性能基线

本文涉及的产品
RDS SQL Server Serverless,2-4RCU 50GB 3个月
推荐场景:
云数据库 RDS SQL Server,基础系列 2核4GB
简介:
Establishing a Performance Baseline

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Baseline performance monitoring involves establishing a performance baseline for your system. A performance baseline includes a single performance chart accompanied by an interpretation of the results, based on your environment. Many elements of the chart, such as the timeframe, vary according to the environment. You can use System Monitor in Windows Server 2003 to establish your performance baseline. The System Monitor chart can be created in real time or based on a performance log file. It is recommended that you base your chart on a log file, because this allows you to record statistics for an extended period.

When establishing your performance baseline, you must select the sampling interval and the server from which to monitor. The sampling interval determines the amount of disk space that your baseline requires. (Using performance counters on the server does not add much overhead to the server running SQL Server.) If you find that your baseline data is taking up too much disk space, you can use a larger interval between data samples. The larger the sampling interval you use, however, the less accurate your graph will be.

You can monitor remotely; however, use of the counters across a network connection for an extended period of time can congest traffic on your network. If you have disk space on your server for the performance log files, it is recommended that you record performance log information locally.

Because of performance impacts related to the number of counters being sampled and the frequency with which sampling occurs, it is important to test the number of counters and the frequency of data collection so you can determine the balance that meets the needs of your environment while still providing useful performance information. For the initial performance baseline, however, it is recommended that you use the highest number of counters possible and the highest frequency available.

Table 5 lists the recommended performance counters to include in your performance baseline.

Table 5   Performance Counters for Baseline Performance Monitoring

 

Object\Counter Definition Recommendations

Memory\Pages/sec

The number of pages read from or written to disk to resolve hard page faults. This counter serves as a primary indicator of the types of faults that cause system-wide delays.

Although it is normal to have some spikes, this counter generally remains at or close to zero.

Network Interface\Bytes total/sec

Number of bytes traveling over the network interface per second. This counter only reflects the local network connection.

If this value stays below 50 percent of your available network bandwidth, the network adapter on the server running SQL Server 2000 is not likely to cause any performance bottlenecks.

PhysicalDisk\Disk Transfers/sec

The rates of read and write operations on the disk. Define a counter for each physical disk on the server.

PhysicalDisk\Avg. Disk Queue Length

The average numbers of both read and write requests that were queued for the selected disk during the sample interval.

The number of requests should not exceed two times the number of spindles constituting the physical disk. If the number of requests is too high, you can add additional disks or replace the existing disks with faster disks.

SQLServer:Memory Manager\Total Server Memory

The total memory in use by SQL Server 2000.

Add memory to the server if this value is generally higher than the amount of physical memory in the server.

SQLServer:Access Methods\Full Scans/sec

The number of unrestricted full scans. These can either be base table or full index scans.

SQLServer:Buffer Manager\Buffer Cache Hit Ratio

The percentage of pages that were found in the buffer pool without having to incur a read from disk.

When this percentage is high, your server is operating at optimal disk I/O efficiency. If this value decreases over time, you might consider adding physical memory to your server.

SQLServer:Databases\Log Growths

The total number of log growths for the selected database.

Run against your application database instance.

SQLServer:Databases Application Database\Percent Log Used

The percent of space in the log that is in use.

Run against your application database instance.

SQLServer:Databases Application Database\Transactions/sec

The number of transactions started for the database.

Run against your application database instance.

SQLServer:General Statistics\User Connections

The number of users connected to the system.

Research any dramatic shifts in this value.

SQLServer:Latches\Average Latch Wait Time

The average latch wait time, in milliseconds, for latch requests that had to wait.

If this number is high, your server might have resource limitations.

SQLServer:Locks\Average Wait Time

The average amount of wait time, in milliseconds, for each lock request that resulted in a wait.

SQLServer:Locks\Lock Waits/sec

The number of lock requests that could not be satisfied immediately and required the caller to wait before the lock was granted.

SQLServer:Locks\Number of Deadlocks/sec

The number of lock requests that resulted in a deadlock.

SQLServer:Memory Manager\Memory Grants Pending

The current number of processes waiting for a workspace memory grant.

For information about how to use System Monitor to create performance charts and logs, see “Monitoring performance” in Help and Support Center for Windows Server 2003.




    本文转自 Fanr_Zh 博客园博客,原文链接:http://www.cnblogs.com/Amaranthus/archive/2011/04/10/2011670.html,如需转载请自行联系原作者



相关实践学习
使用SQL语句管理索引
本次实验主要介绍如何在RDS-SQLServer数据库中,使用SQL语句管理索引。
SQL Server on Linux入门教程
SQL Server数据库一直只提供Windows下的版本。2016年微软宣布推出可运行在Linux系统下的SQL Server数据库,该版本目前还是早期预览版本。本课程主要介绍SQLServer On Linux的基本知识。 相关的阿里云产品:云数据库RDS SQL Server版 RDS SQL Server不仅拥有高可用架构和任意时间点的数据恢复功能,强力支撑各种企业应用,同时也包含了微软的License费用,减少额外支出。 了解产品详情: https://www.aliyun.com/product/rds/sqlserver
相关文章
|
24天前
|
关系型数据库 Serverless 测试技术
评估特定业务场景下扩缩容操作对性能的影响的方法
通过以上多种方法的综合运用,可以较为全面、准确地评估特定业务场景下扩缩容操作对 PolarDB Serverless 性能的影响。这有助于制定合理的扩缩容策略,确保业务系统在不同资源配置下都能保持良好的性能表现,满足业务需求。
20 1
|
24天前
|
数据挖掘 关系型数据库 Serverless
利用数据分析工具评估特定业务场景下扩缩容操作对性能的影响
通过以上数据分析工具的运用,可以深入挖掘数据背后的信息,准确评估特定业务场景下扩缩容操作对 PolarDB Serverless 性能的影响。同时,这些分析结果还可以为后续的优化和决策提供有力的支持,确保业务系统在不断变化的环境中保持良好的性能表现。
27 2
|
5月前
|
搜索推荐 开发工具
通用快照方案问题之性能指标的优化如何解决
通用快照方案问题之性能指标的优化如何解决
51 0
|
安全 定位技术 数据中心
Salesforce诊断网络问题以排除性能下降
Salesforce诊断网络问题以排除性能下降
|
云安全 监控 安全
配置基线对于数据安全的影响
配置基线对于数据安全的影响
205 0
|
atlas Android开发 开发者
构建与基线发布 | 学习笔记
简介:快速学习构建与基线发布
251 0
构建与基线发布 | 学习笔记
|
机器学习/深度学习 监控 安全
监控模型在监控模型在生产环境的性能(Arize)
随着机器学习基础设施的成熟,对模型监控的需求激增。不幸的是,这种不断增长的需求并没有形成一个万无一失的剧本,向团队解释如何来衡量模型的性能。
|
Kubernetes 供应链 安全
以 Log4j 为例,如何评估和划分安全风险
开源软件支撑着绝大多数面向互联网的应用程序。这类项目的可用性、可获取性和质量提升了企业的创新能力,并帮助它们取得成功。它们是很好的公共产品,应该受到赞美和保护。
163 0
|
弹性计算
【新功能】新增实例健康诊断进一步提升自服务能力
随着用户量骤增,阿里云ecs控制台提供几乎接近完美自助修复的能力。自助完成ECS实例连接和访问等常见问题的诊断和修复建议,提高问题解决效率,进而提升用户体验与粘性,大大简化了实例的操作性和维护成本。
2966 0
【新功能】新增实例健康诊断进一步提升自服务能力
|
弹性计算 Java
AutoScaling 成本优化模式升级--混合实例策略
伸缩组成本优化模式以成本为目标,始终创建最低价的实例,同时,通过多可用区,多实例规格分布,以此来提高服务稳定性。但是,对于成本优势最大化的竞价实例,伸缩组难以防范竞价实例大范围回收可能导致的服务雪崩,本次升级允许用户制定更详细的成本控制策略,在成本和稳定性之间进行调整和权衡。
14205 0