So here I am, sitting in a bar, at an airport, trying to figure out why my flight is over an hour late …
It occurs to me that the processes involved with flights are probably the cause of this, and it dawns on me that a poor process is as much a performance bottleneck as a poorly written piece of software is !!!
The flight was late, according to the lady at the counter, because it left late from the previous airfield. That was something I had figured out by myself, but this seemed to be a perfectly acceptable explanation for her. I of course wanted to know WHY the plane left later than scheduled, but that was something she could not help me with. Read More »
I won’t go into the details of the specs of the hardware or OS, since there is no reliable way to compare two different systems against each other, but the relative performance on the tested system gives a very good insight as to how it will behave on other systems as well.
I also want to stress that the SOAP API is not the same as the web/desktop client, and may use a different communication model on the server side. The results ARE NOT comparable to the web or desktop client response times.
Read More »
I recently tested a service that had a Digital Signature system option. At first the Digital Signatures where not enabled, and we were happily testing and getting around 500 ms response times for the service.
Then the Digital Signatures where enabled, and we had to first sign the messages sent, then the server needed to verify the signatures as well.
This turned out to be a major CPU and TIME hog, since on average, regardless of load the verification of the signature took around 200 ms to perform. This made the allover response times increase to around 700 ms for each transaction (200 ms is around 28.5% of 700 ms!). Read More »