Category: Uncategorized

Google Feed Reader: YUCK!

Ok, I thought I was missing something about the Google Feed Reader. I thought it was clumsy and flashy and mostly usefless for the way I read blogs.
Chris Selland makes me feel less alone. [here]
Paul Kedrosky is not amused. [here]
Brad Hill says interesting, but call me when you’re ready. [here]
Bud at The Community Engine says that it is not user-friendly. [here]
Sean Coon: flashy AJAX + proprietary sandbox == Google wants to own your experience. [here]
GoogleÂ’s UX staff take a vacation, return to horror and destruction
I’m sticking with Rojo.


Technorati:
IceRocket:

Level3 and Cogent Reconnected…For Now


UPDATE: Geek News Central sees it another way. They see Cogent as hitching a free ride and getting thrown off the bus finally. Either way, the bacbone providers are about to realize that they aren’t the ones with power anymore.
The lawsuits from this should be interesting, and are likely going to expose many of the dark edges of the connectivity market that will shock most people who use the Internet.


Cnet has the news here.
One of the sites most notably affected was the Boston Museum of Fine Arts — quoted in this story. So I took the MFA as a bellweather of when the Internet would return to normal.


CLICK IMAGE

Using the GrabPERF system and one other measurement network, it appears that the Level3 and Cogent networks started speaking to each other again at approximately 16:00 EDT (20:00 GMT) today, with recovery times varying by company, backbone, and location.


CLICK IMAGE

I was having a conversation on a completely unrelated matter with one of the journalists who covers the Internet space, and mentioned this event to him. He hadn’t heard of it (hey, I know how hard he works), but we both were kind of shocked that this could still happen.
A large backbone provider rarely does this just because they can; if that were the case, the Internet would be divided into petty fiefdoms where no one could talk to anyone else, which sounds awfully familiar to some of us who remember pre-Internet networks.
A large backbone provider does this to strengthen their position, and diminish that of their peering partner.
There is a lot of money being made on the Internet again. This breakage was, in my opinion, is a result of the Tier 1 backbone providers staking out their turf for what they see as another flow of big and stupid spending resulting from the frenzy around Web 2.0.
Level3 summarily terminated the peering arrangement in an attempt to marginalize Cogent, perhaps in an attempt create the impression that Cogent is less valuable to the Internet than “real” Tier 1 backbones.
What does this pre-emptive attack on Cogent’s reputation gain them? I think that the core reason is that Level3 may be trying to reduce the perceived market value of Cogent, making them a more vulnerable target for acquisition.
It will be interesting to watch what happens in a month when this flares up again.


IceRocket: , , ,
Technorati: , , ,

GrabPERF: Non-Subscriber Services Minmized to Index Overviews

GrabPERF is slowly winding down as a public-facing entity. All that is left for non-subscribers are the Search and News Index Overviews.
I will continue to use the data as a demonstration tool, and graphs and data will dot my my blog posts.
And remember, the whole system is on the block; no reasonable offer will be dismissed.
Thanks for your comments and support over the last few months. It’s been a great run.

Level3: Your homepage poorly constructed.

Dear Level3:
Your homepage is full of useless empty spaces, including a very large screen full of empty space after the server response. Have you not heard of HTTP Compression?
At least I know you are using what used to be called ColdFusion to manage your content; ColdFusion is notorious for leaving large gaping holes in a Web page web the application code is stripped away for presentation.
Why would I by transit from a company that seeks to maximize their own bandwidth usage, not conserve it?

GrabPERF: Think you have Packet Loss? This is what it looks like

So, I mentioned earlier that I have packet loss on the uplink from my Web server where GrabPERF and this blog are hosted. How do I know it’s packet loss and not some other issue?


CLICK THE IMAGE

Notice the banding of measurements around 3 and 9 seconds? These values are the set TCP re-transmission timeouts for new connections for almost every operating system. When you see this pattern, check your packet loss stats from your routers/switches/network equipment.
Now…I wonder what my connectivity provider has mucked up?

Copyright © 2025 Performance Zen

Theme by Anders NorenUp ↑