性能数据的收集与数据处理

1、性能数据的收集与数据处理打开历史性能数据收集检查NavisphereAnalyzer使用许可是否已经安装。在Navisphere管理界面，右键选择阵列属性，查看Software页面。如下图，NavisphereAnalyzer使用许可已经安装打开Analyzer Data logging界面。右键点击阵列AnalyzerData Logging在Data Logging界面，选中Periodic Archiving，选择相应的数据收集时间，点击Start可以开始收集性能数据。系统收集的性能数据，每5小时生成一个文件。到达设定的天数后，性能数据收集回自动停止历史性能数据的下载与数据文件合并性能数

2、据下载右键点击阵列AnalyzerRetrieve Archives，选中需要下载的performance archives,点击Retrieve下载。性能数据文件合并在默认时间间隔下，性能数据文件每5Hr左右生成一个。如果需要观察一个较长时间的性能数据，需要将多个性能数据文件合并为一个文件。在Navisphere Manager管理界面，选中ToolsAnalyzerArchiveMerge选择需要merge的性能文件，点击merge进行文件合并。如果文件较多，可使用如下的命令进行文件合并的批处理naviseccli analyzer -archivemerge -data CKM00101

3、700179_SPA_2010-11-01_14-16-48-GMT_P08-00.nar CKM00101700179_SPA_2010-11-01_19-28-48-GMT_P08-00.nar -out merge1.narnaviseccli analyzer -archivemerge -data merge1.nar CKM00101700179_SPA_2010-11-02_00-40-48-GMT_P08-00.nar -out merge2.narnaviseccli analyzer -archivemerge -data merge2.nar CKM00101700179

4、_SPA_2010-11-02_05-52-48-GMT_P08-00.nar -out merge3.narnaviseccli analyzer -archivemerge -data merge3.nar CKM00101700179_SPA_2010-11-02_11-04-48-GMT_P08-00.nar -out merge4.narnaviseccli analyzer -archivemerge -data merge4.nar CKM00101700179_SPA_2010-11-02_16-16-48-GMT_P08-00.nar -out merge5.narnavis

5、eccli analyzer -archivemerge -data merge5.nar CKM00101700179_SPA_2010-11-02_21-28-48-GMT_P08-00.nar -out merge6.narnaviseccli analyzer -archivemerge -data merge6.nar CKM00101700179_SPA_2010-11-03_02-40-48-GMT_P08-00.nar -out merge7.narnaviseccli analyzer -archivemerge -data merge7.nar CKM00101700179

6、_SPA_2010-11-03_07-52-48-GMT_P08-00.nar -out merge8.narnaviseccli analyzer -archivemerge -data merge8.nar CKM00101700179_SPA_2010-11-03_13-04-48-GMT_P08-00.nar -out merge9.narnaviseccli analyzer -archivemerge -data merge9.nar CKM00101700179_SPA_2010-11-03_18-16-48-GMT_P08-00.nar -out merge10.narnavi

7、seccli analyzer -archivemerge -data merge10.nar CKM00101700179_SPA_2010-11-03_23-28-48-GMT_P08-00.nar -out merge11.narnaviseccli analyzer -archivemerge -data merge11.nar CKM00101700179_SPA_2010-11-04_04-40-48-GMT_P08-00.nar -out merge12.narnaviseccli analyzer -archivemerge -data merge12.nar CKM00101

8、700179_SPA_2010-11-04_09-52-48-GMT_P08-00.nar -out merge13.narnaviseccli analyzer -archivemerge -data merge13.nar CKM00101700179_SPA_2010-11-04_15-04-48-GMT_P08-00.nar -out merge14.narnaviseccli analyzer -archivemerge -data merge14.nar CKM00101700179_SPA_2010-11-04_20-16-49-GMT_P08-00.nar -out merge

9、15.narnaviseccli analyzer -archivemerge -data merge15.nar CKM00101700179_SPA_2010-11-05_01-28-48-GMT_P08-00.nar -out merge16.narnaviseccli analyzer -archivemerge -data merge16.nar CKM00101700179_SPA_2010-11-05_06-40-48-GMT_P08-00.nar -out merge17.narnaviseccli analyzer -archivemerge -data merge17.na

10、r CKM00101700179_SPA_2010-11-05_11-52-49-GMT_P08-00.nar -out merge18.narnaviseccli analyzer -archivemerge -data merge18.nar CKM00101700179_SPA_2010-11-05_17-04-48-GMT_P08-00.nar -out merge19.narnaviseccli analyzer -archivemerge -data merge19.nar CKM00101700179_SPA_2010-11-05_22-16-48-GMT_P08-00.nar

11、-out merge20.narnaviseccli analyzer -archivemerge -data merge20.nar CKM00101700179_SPA_2010-11-06_03-28-48-GMT_P08-00.nar -out merge21.narnaviseccli analyzer -archivemerge -data merge21.nar CKM00101700179_SPA_2010-11-06_08-40-48-GMT_P08-00.nar -out merge22.narnaviseccli analyzer -archivemerge -data

12、merge22.nar CKM00101700179_SPA_2010-11-06_13-52-49-GMT_P08-00.nar -out merge23.narnaviseccli analyzer -archivemerge -data merge23.nar CKM00101700179_SPA_2010-11-06_19-04-48-GMT_P08-00.nar -out merge24.narnaviseccli analyzer -archivemerge -data merge24.nar CKM00101700179_SPA_2010-11-07_00-16-48-GMT_P

13、08-00.nar -out merge25.narnaviseccli analyzer -archivemerge -data merge25.nar CKM00101700179_SPA_2010-11-07_05-28-48-GMT_P08-00.nar -out merge26.narnaviseccli analyzer -archivemerge -data merge26.nar CKM00101700179_SPA_2010-11-07_10-40-48-GMT_P08-00.nar -out merge27.narnaviseccli analyzer -archiveme

14、rge -data merge27.nar CKM00101700179_SPA_2010-11-07_15-52-48-GMT_P08-00.nar -out merge28.narnaviseccli analyzer -archivemerge -data merge28.nar CKM00101700179_SPA_2010-11-08_02-16-48-GMT_P08-00.nar -out merge29.nar性能分析简介设置Analyzer属性在Navisphere Manager管理界面，选中ToolsAnalyzerCustomize在general界面，选中Advance

15、d。在Archives界面，选中Performance Detail，不选择Initially check all tree objects.使用Analyzer打开历史性能文件在Navisphere Manager管理界面，选中ToolsAnalyzerArchiveOpen文件打开后出现一下界面，显示了性能数据的开始和结束时间。可以选择其中一部分时间段进行数据分析。Perfermance detail界面出现后，可以选择性能分析的对象，对象可以是SP，LUN，RaidGroup，Disk等等。例如：这里选择了SP对象类型，一共有两个对象，SPA和SPB。根据所选对象的不同，不同对象有不同的

16、性能属性可以选择。例如：这里对SP的Utilization进行分析。常规性能分析检查点Performance Analyzer可以分析的性能参数很多，以下仅列出常规性能检查的一些参数及其介绍。其他参数，请参考Navisphere Manager Help。SP性能参数UtilizationDescribes the fraction of a certain observation period that the system component is busy serving incoming requests. An SP or disk that shows 100% (or close

17、 to 100%) utilization is a system bottleneck since an increase in the overall workload will not affect the component throughput; the component has reached its saturation point. Since a LUN is considered busy if any of its disks is busy, LUN utilization usually presents a pessimistic view. That is, a

18、 high LUN utilization value does not necessarily indicate that the LUN is approaching its maximum capacity.Response Time (ms)The average time, in milliseconds, required for one request to pass through a system component, including its waiting time. Total Throughput (IO/s)The average number of reques

19、ts that pass through a system component per second. Total throughput includes both read and write requests.Total Bandwidth (MB/s)The average amount of data in Mbytes that is passed through a system component per second. Total bandwidth includes both read and write requests.Dirty Pages (%)Advanced On

20、lyPercentage of cache pages owned by this SP (pages committed to cache, but not yet written to disk). In an optimal environment, the dirtys percentage will not exceed the high watermark for a long period.High Water Flush On Advanced OnlyNumber of times, since the last sample, that the number of modi

21、fied pages in the write cache reached the high watermark. The higher the number, the greater the write workload coming from the host.Disk/RaidGroup性能参数UtilizationDescribes the fraction of a certain observation period that the system component is busy serving incoming requests. An SP or disk that shows 100% (or close to 100%) utilization is a system bottleneck since an increase in the overall workload will not affect the component throughput; the component has reache