Archive | Geek Stuff

Shiva The Destroyer

Google is going to roll out an ultra-high-speed broadband network. From Wired:

The announcement is not good news for the nation’s ISPs, which have long had a sour relationship with Google. Although Google interconnects with networks just as any other participant in the internet does, ISPs — including AT&T — have complained that Google properties such as Youtube should pay more to ride on their networks.

For its part, Google sees high ISP subscription fees and the U.S.’s slow connection speeds as hindrances to more profits. In the simplest equation, the more people who are online and the faster their connection, the more money Google makes from little text ads on the net. Any company who wants to make money anywhere between a user and an online ad has to fear that Google will try to drive the profits out of its business, whether that be a hardware vendor, a software company like Microsoft or an internet service provider.

Google is doing at least three things here:

1) It’s demonstrating to the public and to regulators that really fast broadband isn’t nearly as hard as companies like AT&T and Verizon pretend it is.

2) It’s sending a warning to large telecoms that they better start working to reduce prices and increase service or they might face a competitor tney don’t want to go up against, and

3) By partnering with municipalities, it’s learning/showing the nation how to bypass the current dominant telecom players by creating municipally-owned fiber infrastructure that can be rented to multiple service providers, who can then duke it out on price and service. If successful, that could create a model where Google uses its huge cash surplus to finance municipally-owned fiber optic networks, undermining its telecom rivals and speeding up the nation’s internet without ever having to run a consumer-grade network or learn how to do customer support.

If I were an executive at a large ISP, I’d be very unhappy with Google’s announcement. When Google enters a market, it usually destroys traditional ways of making money. ISPs want to find ways to measure internet traffic, and charge users by levels — even as their own upstream bandwidth costs continue to plummet. The rhetoric used to justify those decisions to consumer and lawmakers just won’t hold up if there’s an fairly priced, all-Fiber 1 Gbps connection just down the road.

Which is just the long way of saying that in a land where it costs “$35 a month to get an assymetric, slow DSL line that tops out at 1.5 Mbps, perhaps those traditional profits need to be destroyed.

Or even shorter — All hail Shiva the Destroyer.

Actual consumer choice! Can’t wait.

Duh

Who don’t know that? (via Maya.)

Would it interest you to know that many, many metaphysical traditions say the exact same thing? Many moons ago, I used to date a grad student who was a quantum physicist. He’d tell me all this stuff and get really annoyed when I’d say, “Yeah, I knew that.”

Because, you know, I couldn’t show the work.

#&#@*!!

In case you were wondering why I haven’t been online for the past two days, here’s the explanation from our (former) host:

Unfortunately, your WordPress site is causing what is called “slow queries” on your database server.

A slow query is a query that examines a high amount of rows over a long period of time. The more the query has to examine and the longer the query
takes to do so, the harder it can be on the server. In that you are hosting on a shared hosting server, such queries can become problematic for other users.

WordPress, being a dynamic site, would normally run such queries on every to almost every access on the site. One recommendation would be to setup a
caching utility if you haven’t already, which would prevent the software from having to run so many queries. You may also wish to check with the
Wordpress forums for any thoughts on reducing the impact WordPress might have on a database server.

Here are some example queries that we are referencing:

# User@Host: susiemad[susiemad] @  [209.68.6.23]
# Query_time: 163  Lock_time: 0  Rows_sent: 1  Rows_examined: 32054
SELECT SQL_CALC_FOUND_ROWS  wp_posts.* FROM wp_posts  WHERE 1=1  AND
HOUR(wp_posts.post_date)=’19’ AND MINUTE(wp_posts.post_date)=’8′ AND
YEAR(wp_posts.post_date)=’

2007′ AND MONTH(wp_posts.post_date)=’12’ AND
DAYOFMONTH(wp_posts.post_date)=’24’ AND wp_posts.post_type = ‘post’ AND
(wp_posts.post_status = ‘publish’)  ORDER BY wp_posts.post_date DESC LIMIT
0, 15;

# User@Host: susiemad[susiemad] @  [209.68.6.23]
# Query_time: 191  Lock_time: 0  Rows_sent: 1  Rows_examined: 10328
SELECT p.* FROM wp_posts AS p  WHERE p.post_date < ‘2007-12-21 20:37:49’
AND p.post_type = ‘post’ AND p.post_status = ‘publish’  ORDER BY
p.post_date DESC LIMIT 1;

# User@Host: susiemad[susiemad] @  [209.68.6.23]
# Query_time: 14  Lock_time: 0  Rows_sent: 1  Rows_examined: 64108
SELECT SQL_CALC_FOUND_ROWS  wp_posts.* FROM wp_posts  WHERE 1=1  AND
wp_posts.post_type = ‘post’ AND (wp_posts.post_status = ‘publish’)  ORDER
BY wp_posts.ID ASC LIMIT 0, 1;

# User@Host: susiemad[susiemad] @  [209.68.6.23]
# Query_time: 32  Lock_time: 0  Rows_sent: 1  Rows_examined: 32054
use susiemad_wordpress;
SELECT SQL_CALC_FOUND_ROWS  wp_posts.* FROM wp_posts  WHERE 1=1  AND
HOUR(wp_posts.post_date)=’16’ AND MINUTE(wp_posts.post_date)=’24’ AND
YEAR(wp_posts.post_date)=’2004′ AND MONTH(wp_posts.post_date)=’10’ AND
DAYOFMONTH(wp_posts.post_date)=’31’ AND wp_posts.post_type = ‘post’ AND
(wp_posts.post_status = ‘publish’)  ORDER BY wp_posts.post_date DESC LIMIT
0, 15;

Unfortunately, given the number of problems the database has caused we will have to ask your review of the above and a discussion on correcting the problem prior to our re-enabling the database.

Site Meter