创建性能基线

本文涉及的产品
云数据库 RDS SQL Server,基础系列 2核4GB
RDS SQL Server Serverless,2-4RCU 50GB 3个月
推荐场景:
简介: Establishing a Performance Baseline Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 wit...
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.

相关实践学习
使用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
目录
相关文章
|
4月前
|
SQL 运维 数据库
MSSQL性能调优实战:索引策略优化、SQL查询精细调整与并发管理
在Microsoft SQL Server(MSSQL)的运维与优化过程中,性能调优是确保数据库高效运行的关键环节
|
4月前
|
搜索推荐 开发工具
通用快照方案问题之性能指标的优化如何解决
通用快照方案问题之性能指标的优化如何解决
45 0
|
6月前
|
自然语言处理
LLM上下文窗口突破200万!无需架构变化+复杂微调,轻松扩展8倍
【5月更文挑战第12天】LongRoPE研究突破LLM上下文窗口限制,无需架构变更和复杂微调,实现8倍扩展至2048万个token。该方法利用位置嵌入非均匀性,通过高效搜索和优化初始化,适用于处理长文本任务,对模型性能影响小。但可能需要较多计算资源,且2048万的长度是否足够所有任务尚待探讨。[论文链接](https://arxiv.org/abs/2402.13753)
170 1
|
6月前
|
缓存 算法 测试技术
优化 C#编程性能的策略
【4月更文挑战第20天】优化C#性能策略包括:选择合适算法和数据结构,避免频繁对象创建,缓存常用数据,减少内存分配,使用异步编程,优化数据库操作(如合理查询和使用索引),利用多线程并行处理,精简代码,使用性能分析工具,硬件升级,以及进行性能测试。综合应用这些策略可提升程序性能和响应性。
65 4
|
6月前
服务网格中授权策略对性能的影响大吗?
在使用服务网格时,面对一些大规模集群,大家可能会担心:网格中授权策略内容过于庞大时,对网格代理的性能影响大吗?本文中我们就会给大家简单测试一下:不同情况下,授权策略中配置上万条IP时,对请求影响有多大? 结论:大多数情况下,对请求影响十分微小。
232 1
|
6月前
|
机器学习/深度学习 算法 测试技术
RAG应用程序的12种调优策略:使用“超参数”和策略优化来提高检索性能
本文从数据科学家的角度来研究检索增强生成(retrieve - augmented Generation, RAG)管道。讨论潜在的“超参数”,这些参数都可以通过实验来提高RAG管道的性能。与本文还将介绍可以应用的不同策略,这些策略虽然不是超参数,但对性能也会产生很大的影响。
386 1
|
云安全 监控 安全
配置基线对于数据安全的影响
配置基线对于数据安全的影响
200 0
|
机器学习/深度学习 监控 安全
监控模型在监控模型在生产环境的性能(Arize)
随着机器学习基础设施的成熟,对模型监控的需求激增。不幸的是,这种不断增长的需求并没有形成一个万无一失的剧本,向团队解释如何来衡量模型的性能。
|
编解码 算法 前端开发
Cartographer参数调整来降低延迟的策略
Cartographer参数调整来降低延迟的策略
|
大数据 开发者
R 实例——预测海藻数量之模型的精简和调优| 学习笔记
快速学习 R 实例——预测海藻数量之模型的精简和调优
161 0
下一篇
无影云桌面