Guess Blake and the team at IceRocket don’t want to be measured anymore.

Guess I will disable those measurements — they will remain off until further notice.
Blake got back to me — issue fixed! Yay!
This makes me sad.
A South Caroline businessman is making an attempt to purchase the Hudson’s Bay Company. [here]
The company, lovingly referred to as the Bay, was incorporated in 1670 and once owned more real estate in North America, in fact “all the land in the Hudson Bay watershed – a mass that amounts to about a third of present-day Canada.” [here]
The HBC is the early history of Canada. Without their greed and ingenuity, Canada would never have grown beyond the Valley of the St. Lawrence.
Perhaps this is the revenge for War of 1812.
Technorati: Canada, Hudsons Bay Company
IceRocket: Canada, Hudsons Bay Company
At 2AM EDT Oct 30, 2005, it will become 1AM EST Oct 30, 2005. This shift will take us from GMT -4 to GMT -5.
As always, hang onto your hats, as I have no idea how the time change will affect the graphing in GrabPERF. My theory is that there should be double measurements for the 1 AM hour, and the hourly rollup will fail, as there will already be an entry for the time period.
I could write an exception for this twice yearly foobar, but let’s just say this update is scraping the bottom of the GrabPERF punch-list.
At least I don’t have this problem.
I have been getting Partial File errors out of cURL on the Agent that is running on my home network. These started at around 16:15 EDT October, 28, 2005. This is why the availability for this measurement is running at around 50%.
Now, did the folks at Feedster make a networking/server change around that time?
Need I say anything more?
Thus it began.
Jeff Nolan adds his voice to the TypePad rumblings. [here]
Take away quote:
Some very experienced IT professionals are chiming in that they understand how difficult it is to run a datacenter (something I myself have not done I would add) and I am sure the empathy is well meaning. However, there are ample examples of large datacenter operations that operate with a very high degree of uptime and performance so while running a high capacity and complex datacenter may be difficult, it is being done successfully elseware.
Mena and Ben (further putting the human face on the company, a good PR tactic) may be plenty sorry, but I’m still stuck paying for shitty Typepad performance. In fact, I’d like to see this subscription software model go even further to align with customers by putting a service level agreement (SLA) in place that lays out a series of financial penalties the provider incurs when performance and availability fall below predefined thresholds. I bet they would not have to be sorry then, because companies that have these kinds of service level agreements are always highly motivated to get it right the first time.
Wow. It’s not often you read something like this.
Oh yeah, it’s the blogosphere.
Take away quote:
The question then is: if you ran out of space and were having problems, why did you continue to take on new customers during this period? Surely a responsible business with serious capacity issues would have closed their doors to new business to assure that its current clients were taken care of.
Its called greed.
I’ve been using Ping-O-Matic for a long time, but in the last 2-3 days, it has simply not been responding.
Switched over to Pingoat — hope that works better.
Rojo has started showing unusual performance values over the last 24 hours.
Most of the gain has been in First Byte times — the time between the Client issuing the GET, and the Server’s response arriving back at the Client.
Since I use Rojo, this is a concern for me.
Technorati: Rojo, aggregator
IceRocket: Rojo, aggregator
Copyright © 2025 Performance Zen
Theme by Anders Noren — Up ↑