Author: spierzchala

Ok. Does Gutter Helmet just not get it?

Ok, finally got some action from the people at the Customer Service Centre for Gutter Helmet towards helping us fix the final drip between the house and the gutter. This drip is, of course, right over the back door and targets anyone leaving the house when its raining.

The Customer Service Centre was having some trouble reaching their technician. Lucky for them, the technician was across the street, working on our neighbour’s house. Maybe we should have told them…?

So, I call Samantha, and Samantha goes across the street to ask the gentleman to call in and speak to the rep handling our case.

Samantha called me after she did this and said that the technician did everything short of growl and bare his teeth at her.

Look, Gutter Helmet: your on-the-ground “technicians” are the face of your company (except for the fast-talking sales dudes). This is the third — yes, THIRD — technician we have encountered who has had the customer service skills of a molotov cocktail.

We don’t ask for much; a little civility is all that is required.

“Yes ma’am. The Customer Service Rep got a hold of me and I will come over as soon as I’m done here. Thank you.”

That’s all it takes.
<SIGH>


UPDATE (to the update): When Tracy from the Customer Service Centre called me back to follow-up, I told her that the technician had been and this had been confirmed by Samantha.

I then told her about the technician’s attitude. In fact, it was the same technician who had come out previously, and given us some attitude. And the bad news was, he had also given Tracy some attitude.

Maybe this will be the final post on this topic.

Upgrade to MySQL 5.0.15 Complete

Wait! Didn’t he say he had done this already?
Yup. But forgot one stupid little step. You have to re-compile PHP to work with the new MySQL 5.0 libraries. I tried to restart Apache and it barfed all over the PHP module with MySQL library module mismatch errors…or something like that.
Done and the system is now using the right MySQL libraries.
Usual caveats about system weirdness apply. Operator weirdness is your own issue.

Testing of MySQL 5.0

Ok Everyone, if you start seeing some odd behaviour from my sites (GrabPERF, Newest Industry, Pierzchala.com), it’s because I am doing some testing to see if the scripts, processes, and applications I have built on top of MySQL 4.1 can stand the upgrade.
I will not be upgrading the primary database system until all of this testing is complete.

Venetian Server Room

Have I ever mentioned that when it rains, water comes into our basement?
Have I ever mentioned that said water flows less than an inch directly below the only place in the house my servers can go?
Ugh.

GrabPERF: Comparing Technorati Blog and Tag Search

Normally when I discuss the performance of a page I am measuring using GrabPERF, it’s either good news (“you just got 5 times faster!”) or bad news (“your page hasn’t loaded in 6 months; you still there?”).
Today, something a little different: a question. What’s the question?

Why is the performance of a Technorati Blog (aka Traditional) Search so different from a Technorati Tag Search?

For those of you who have been around for a while, you know that Technorati allows you to search for results based on a Traditional search engine methodology, which is date-ranked, most recent first. It also provides a way to search through the user-defined tags that are appended to posts, or listed as category titles.
The issue that I have been seeing from my measurements is that Tag Searching is performance substantially worse than Traditional Search.


TRADITIONAL SEARCH



TAG SEARCH

What I need to understand from the Technorati team is the particular technical challenges that differentiate Traditional v. Tag Searching, because the difference in performance is astonishing.
And then there is the success rate of the Tag Search.


TECHNORATI TAG SEARCH SUCCESS RATE

When I examine the data, almost all of the errors on the Tag Search measurement are Operation Timeouts. I have set the GrabPERF Agent to time out when no response has come back for the server in 60 seconds. So, effectively 15% of the Tag Searches do not return data to the client in 60 seconds.
So, while the Traditional Search has been tuned and optimized, there appears to be much work left to make the Tag Search an effective and useful tool.


Technorati: , , ,
IceRocket: , , ,

Copyright © 2025 Performance Zen

Theme by Anders NorenUp ↑