Categories: Problem Analysis, Workload Analysis | Author: Sam | Posted: 18/05/2017 | Views: 91

Part 1 in a series of posts focusing on how we gather and analyse data for a performance project. Clear requirements gathering is key to a successful, and most importantly, meaningful, performance test engagement. Identifying clear; non-functional, infrastructure, and test set-up requirements for the performance testing, will play a critical role in the completion of a valuable performance engagement. 

Read More...


Categories: Problem Analysis | Author: Owen | Posted: 29/07/2016 | Views: 175

Not all performance issues are found during formal performance tests. A significant number are found during performance test smoke testing or other debugging activities. The one described below was found during an exercise to see if Splunk would provide any useful information from the application logs being generated on a multi-tier application.

Read More...


Categories: Our Thoughts | Author: Owen | Posted: 14/07/2016 | Views: 167

Dots vs lines, which is better? When should I use one over the other? Should I even care? The boss just wants a pretty picture in the report, I’ll can use whatever the default is and go to lunch early.

Read More...


Categories: Our Thoughts | Author: Scott | Posted: 15/05/2016 | Views: 333

In a recent engagement, we were faced with a little bit of a conundrum – a limited to non-existent tools budget versus a requirement to performance test a SAP-NWBC (NetWeaver Business Client, what was once called SAP-Web) deployment with volumes of up to 4000 concurrent users. Usually when dealing with SAP, LoadRunner is one of the go-to tools on the market.

Read More...


Categories: Our Thoughts | Author: Owen | Posted: 15/10/2015 | Views: 346

Donald E. Knuth is credited with stating; “The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming”. Much has been said both for and against this statement in the 40 odd years since it was coined. I'm no developer so I can't speak too much to the relative merit or weakness of the quote nor how much of the context the quote was made in still applies today. However, I have worked in software development for some time and believe that the sentiment of the quote should be applied to a much wider problem set such as system design.

Read More...


Page 1 of 2First   Previous   [1]  2  Next   Last