In part 1 of this article, I looked at raw performance numbers of the TestTrack SDK. Interesting data but no pretty pictures!
We saw the performance differences between IIS and Apache on the Windows server. If you graph the results though, you’ll see that the difference is very minor.

Chart 1: Apache vs. IIS in calling getRecordListForTable, timing for entire query
Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Every so often we are asked for performance metrics on the TestTrack SDK, but unfortunately we don’t have any standard metrics as far as timing and footprint. Performance is also critical for most of the integrations we do and, while we test that on an individual project basis, it would be helpful if we also knew baseline numbers for the SDK itself. JMeter is a tool I’ve been meaning to look at for awhile and I finally found time to take it for a spin. My goal was to compile some statistics on TestTrack SOAP SDK performance and scalability. Quite a lot of possibilities to test but I’m going to look at just record query performance in two posts I’ll publish over the next couple of weeks.
Getting Started
First I had to learn JMeter, and luckily they have quite a bit of quality documentation so the learning curve was minor. It only took me an hour or so to get a simple test plan up and working to pull the project list, login and logoff. Once that was up, it was just a matter of defining the test scenario.
Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
I recently got a call from our Support manager about a customer who was upset that TestTrack “wasn’t working and was performing horribly” and they were not happy with us. Support had already confirmed that it wasn’t a functionality issue so there wasn’t much else they could do. They asked me if I would I be able to at least review the customer’s setup? So I took the call and 2 minutes into it I knew there was something completely out of whack with their implementation.
First, the company was a supplier to BMW and the “horrible performance” was in exchanging data through the BMW defect exchange interface. We’ve done several implementations of exactly that interface over the past couple of years without any performance issues.
Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon