这个周末终于有点时间，把订阅的某个博客里这段时间积压的新文章翻了翻。现在做一个简单的笔记，以免很快就遗忘了。
文章一：How to identify IE Add-Ons such as Skype that impact Web Site Performance
页面加载显示慢，需要的时间长，分析其时间的消耗，排除在下载网络资源上（通过一些工具来跟踪浏览器和服务器的交互和时间消耗，比如，Chrome自带开发工具），那么就可以判断是客户端的影响，此文章里，是Skype的插件影响的。
文章二：When DB Log files don't help: Data Access Analysis Tips to boost Performance
文中最后的结论是，性能测试最好不用特殊测试帐号，最好是使用跟最终用户差不多的用户（包括设置，数据等），以免带来意料之外的影响。
文章三：DevOps is Changing the M in APM: Performance Requires Management – Not Monitoring
文章提到DevOps应该转变单纯的Monitor即监控，应该是管理，为产品服务，为提交高质量的产品的服务。
- Management Requires Collaboration; Monitoring Does Not.
- Management Requires Expertise; Monitoring Does Not.
- Management Prevents Problems; Monitoring Does Not.
里面提到三点，合作，专业，预防问题（也含积极解决问题）。
突然有些想法，是不是由于现代详细的分工造成的，开发只开发，测试只测试，运维只运维。没有人人为产品服务的意识，没有人人对产品负责的意识，只是完成份内的工作，这么一来，大家很可能是以厚黑学中的"断箭法"办事，实际上这种状态对产品并不是好事。好在目前敏捷在推跨功能团队，DevOps，以及微软、谷歌的开发和测试角色，似乎也有之前的分工又融合的样子。或者可以说，一个组织里需要大部分的是通才（融合），少部分的是更深入的专才（分工）。
文章四：I'm Not Scared of DevOps and you Shouldn't be Either
The Foundation of DevOps
CAMS (Culture, Automation, Measurement, Sharing) are 4 key areas that are core to the DevOps movement. Culture is the hardest to change but is also the most important because it means a change in the way in which the different teams work together and share the responsibility for the end users of their application. It promotes the usage of development practices in operations to automate deployment. It also allows developers to learn from "the real world" Ops experience and with that mutual exchange it breaks down the walls.
文章五：DevOps Survival Guide: 2013 Online Holiday Shopping Season
里面其中有一个小节提到从去年 - 2012年看到了学到了一些情况，需要注意的。
- 3rd Party Impact on Performance - 第三方的控件、页面元素会影响到性能
- Mobile taking over the Business - 移动越来越流行，更多人通过移动设备访问网站
- Lack of "basic" WPO - 基本网页、网络优化，最佳实践都没有做
- Predicting Traffic - 根据去年的访问数据，设立今年的预期的访问量
文章六：With Confidence into the Holiday Season: Verifying Readiness in Test / Pre-Production
再次以假期销售旺季，电子商务网站为背景，结合性能测试步骤，说了些更具体策略和方向（包含手机应用的注意项）。
对我这种新手来说，再次重复的步骤更加印象深刻，如下：
- Step 1: Preparing your tests
- Question #1: Identify Key Landing Pages, User Interactions and Conversion Funnel Actions
- Question #2: Identify additional Use Case Scenarios
- Question #3: Identify the types of your End Users
- Question # 4: Identify involved 3rd parties
- Step 2: Sanity Checks - checks on basic WPO (Web Performance Optimization) rules as well as testing the end-to-end functionality of your use cases
- Step 3: Throughput Tests - verifies if the system can withstand the busiest peak period
- Step 4: Concurrency Tests - withstanding constant high load over a long period of time
- Step 5: Real End User Tests
- Step 6: Test Monitoring and Alerts for Production