ThoughtWorks
  • 联系我们
  • Español
  • Português
  • Deutsch
  • English
概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

    智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 低摩擦的运营模式

    提升组织的变革响应力

    企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

    合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
概况

特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
  • Español
  • Português
  • Deutsch
  • English
ThoughtWorks菜单
  • 关闭   ✕
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们
  • 返回
  • 关闭   ✕
  • 概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

  • 低摩擦的运营模式

    提升组织的变革响应力

  • 智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

  • 企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 返回
  • 关闭   ✕
  • 概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
  • 返回
  • 关闭   ✕
  • 概况
  • 特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

  • 数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

  • 所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

  • 返回
  • 关闭   ✕
  • 概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

  • 返回
  • 关闭   ✕
  • 概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
博客
选择主题
查看所有话题关闭
技术 
敏捷项目管理 云 持续交付 数据科学与工程 捍卫网络自由 演进式架构 体验设计 物联网 语言、工具与框架 遗留资产现代化 Machine Learning & Artificial Intelligence 微服务 平台 安全 软件测试 技术策略 
商业 
金融服务 全球医疗 创新 零售行业 转型 
招聘 
职业心得 多元与融合 社会改变 
博客

话题

选择主题
  • 技术
    技术
  • 技术 概观
  • 敏捷项目管理
  • 云
  • 持续交付
  • 数据科学与工程
  • 捍卫网络自由
  • 演进式架构
  • 体验设计
  • 物联网
  • 语言、工具与框架
  • 遗留资产现代化
  • Machine Learning & Artificial Intelligence
  • 微服务
  • 平台
  • 安全
  • 软件测试
  • 技术策略
  • 商业
    商业
  • 商业 概观
  • 金融服务
  • 全球医疗
  • 创新
  • 零售行业
  • 转型
  • 招聘
    招聘
  • 招聘 概观
  • 职业心得
  • 多元与融合
  • 社会改变
软件测试Pune技术

From 3 minutes to 3 seconds

Preeti Mishra Preeti Mishra

Published: Nov 24, 2014

Imagine you’re surfing through the web and all the pages show you the wait spinner for 15 seconds. How long would you continue to surf without losing your patience? How long until you move to doing something else? What if one website does this to you? Would you visit that page again without complaining? Would you recommend the website to anyone else? 

Most users reject web applications when they take more than 4 or 5 seconds to load. Performance is a key factor for user adoption. And one of the key determinants of performance is geography. Let’s say the site works perfectly well for our country. Do we even think about its performance in other regions? Or on different mobile networks?

A rather sluggish app

I am the QA for a ThoughtWorks' sales application. Our users are out in the field most of the time and they need a quick, mobile-friendly way to input data into our sales systems. After announcing the initial release of our app, some of our users complained that the app’s response time was too slow and consequently they were unable to use the app. A series of video calls revealed the performance issues that these users were facing. We saw that it actually took around 3 minutes to load each page, which was obviously too slow for anyone to make use of the app.

Diagnosing the issue 

Having seen the issues, we brainstormed some potential causes for poor performance. Here’s what we thought could be the case:

  • We might have been testing on unrealistically high speed internet. Until then, we had tested the app on office wi-fi networks.  Out in the field, the application would probably be run on mobile 2G/3G or average speed wi-fi networks.
  • The servers were close to our region and there might be a chance that more remote regions were all suffering from latency and / or packet-loss.
  • It could be that a country-specific firewall was interfering with some of our requests.

We had a bunch of possibilities in front of us, but we couldn’t be sure of the real cause yet. 

Getting to the real culprit

Among all the above possibilities, we had to figure out the actual cause of this performance problem. We adopted the method of elimination to get to the root of this.

We first tested locally on 2G and 3G mobile networks. Our users helped us a lot in this by testing in different locations; indoors, out in the cities, as well as some remote areas. Most of them seemed quite satisfied with the results. In some areas where the mobile network coverage was not very good, we saw a few problems. Overall though, the application’s response time was close to acceptable limits. 

In order to rule out latency and packet loss issues, we set up calls with our users in every region; Africa, Asia, Australia, Europe, North and South America. As it turned out, no region experienced any performance issues and everyone, with the exception of one country, was quite comfortable using the application. It was soon evident that our issue was specific to that country’s firewall.

Solving the problem

We spoke to other ThoughtWorks teams who support applications in that country to understand how they deal with performance problems there.  It turned out that most of these apps were on internal office networks, so their setup was not equivalent. 

We started testing the connection with pings to the app from that region. The response times were good, which confused us. After some investigation, we learned that the firewall filters traffic at the TCP layer.  Pings send lower-level ICMP (IP) packets. These pass right through the firewall with little or no delay. This meant that we could use ping to test that a network path existed, but could not assume that communication would be fast or even permitted.

We then set up two computers, one to run the app and one to video the other computer. We connected the video computer to a separate network from the application computer so that the video stream didn't interfere with the application’s performance.  This was particularly important when testing on mobile networks where bandwidth is constrained.  

We studied the network traffic for each type of network; office-private wifi, public wifi, and mobile 3G.  We learned that it is important to test on multiple mobile providers as they each implement the government’s blacklist in their own way.  

Our learnings and optimisations follow.

Small changes, big impacts

  • Google properties were blocked in this country. Hence, fonts.googleapis.com was not accessible. This meant that the page waited until the request timed out (60s) before loading the rest of the page. We mitigated the issue by downloading the fonts and serving them from our server. This greatly improved performance.
  • Our analytics tool was not blocked, but was slow to download from its own site and delayed the loading of other assets.  We made two improvements here. We now serve it up from our server and we do so in parallel with other assets so as not to delay their loading.
  • Previously, static assets were minified but not compressed, which slowed load time. Enabling compression in our web server compressed them to 1/4 their previous size.
  • Many other AJAX calls were run sequentially.  Most of these now run in parallel.

After making the above changes the page response time dropped to 3-5 seconds depending on the internet connection. Our users were very happy with our quick turnaround time. We continued to check in with them periodically to ensure that nothing has fallen apart. Furthermore, while analysing stories we kept these points in mind and implemented them in such a way that our users won't have to go through this kind of trouble again. 

And so, we learnt...

From this experience, we learned to consider a whole new dimension that we’d clearly missed at the start. 

  • Depending on the needs of the application, the analysis and requirements should consider from the start how geography could affect performance and other cross-functional requirements.
  • User testing should be an integral part of the Software Development Lifecycle. As time passes, cost of fixing tends to get increasingly expensive. 
  • Testing on 2G, 3G and other mobile data networks is essential for mobile apps, especially in the locations where the users will use them.
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们

WeChat

×
QR code to ThoughtWorks China WeChat subscription account

媒体与第三方机构垂询 | 政策声明 | Modern Slavery statement ThoughtWorks| 辅助功能 | © 2021 ThoughtWorks, Inc.