4 tips and tricks for mobile performance

In case you missed our mobile web seminar on Wednesday, May 21st, we are sharing some tips and tricks for mobile developers and testers. These can be used throughout development, testing, and production to verify their mobile app performance across multiple platforms.

 

Testers and developers need a comprehensive, enterprise grade toolset that addresses the major variations in platforms, browsers, and operating environments. It is no secret that mobile device fragmentation—especially with the many Android device flavors—has made performance testing mobile software much more difficult. Teams must support many mobile web and native programming approaches.

 

You can also learn more in this whitepaper: “Mobile Load: Performance testing for mobile application...

 

Here are a few categories to consider:

 

Don’t just fix, fix value streams

Event to fix.png

 

If organizations only fix what customers explicitly complain about, they may pay a high price. Industry leadership in efficiency is achieved through mitigating risks by preventing and avoiding the extra costs of operating in emergency mode.  By doing this, organizations can shift from resolving disruptive events to fixing value streams that decrease risk and encourage innovation. The key to treating performance testing is an investment; just like a decision to buy insurance for a home or car.

 

Prepare to shift performance quality forward

shift performance qulaity forward.png

 

Sometimes, organizations don’t allocate enough time to implement a mobile application. Instead of delaying performance until the very end—when very little can be done without major disruption—organizations should make performance a part of each product increment delivery.  This is a trend known as “shift left.”  By doing this operations can validate their server setup automation. Developers can get various features to work cooperatively. System Administrators can have realistic trigger points.  Performance Engineers can correctly emulate load on servers. With everyone working together, “performance quality” leads to achieve efficiency and reliable results.

 

Address risks across topologies incrementally and automate deployment variations

 

address risks.png

 

Often times, a system may start on a developer’s local server with all the components on one portal machine.  As a system matures, it often runs on different arrangements of hardware and software to a QA configuration in a private cloud which has a separate database.

In staging, the various components are usually separated to verify configurations. HP automates using reusable topology models that define test sets used for scheduling automated builds of what developers create, and run overnight. It then produces logs and reports for the whole team to analyze. The key is the ability for people to manage whole environments and also provision infrastructure where apps can be deployed and run repeatedly. This reusability, self-service, tuning, and comparing is what enables earlier exposure of risks.

 

Measure Exposure to Performance Risks

 

Finally, here is a brief list to consider when measuring exposure to performance risks:

 

  • Slow network
  • Spikes in network and server
  • Page loads too many resources
  • Server spike capacity bottlenecks
  • Internal contention
  • More hardware doesn’t increase capacity as expected
  • Servers underutilized

 

HP LoadRunner with HP Network Virtualization were designed with all of these issues in mind, from the end user to the client, to application servers and the database.  HP created the mobile performance testing process for organizations that emulate many real users by authoring scripts in test scenarios. .  In the meantime, we invite you to visit us at our home page: hp.com/go/loadrunner and tweet us your thoughts @HPLoadrunner!

 

 Tips and Tricks Webinar.PNG

 

 

 

 

Make sure you watch our next webinar:

June 18th , 2014 – 12 pm EDT

Continuous Integration: Agile and performance testing (Silvia / Shane)

Register here

 

You can also learn more in this whitepaper: “Mobile Load: Performance testing for mobile application...

 

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
About the Author
WW Sr Product Marketing Manager for HP ITPS VP of Apps & HP Load Runner


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation