Slow speed on appspot.com with custom domain enabled

[Brandon Thomson]

Hi, I have my app conquer-on-contact setup to serve through conquer-on-
contact.bthomson.com. The app still works through appspot.com but it
seems to be much slower than through bthomson.com for some reason.
This makes it hard to test new versions of my app since I can only do
that through appspot.

Example:

wget http://conquer-on-contact.bthomson.com/js/jquery.js
100%[==================>] 57,254 207K/s in 0.3s

bthomson@ubuntu-wintendo:~$ wget http://conquer-on-contact.appspot.com/js/jquery.js
100%[==================>] 57,254 14.7K/s in 3.8s

bthomson@ubuntu-wintendo:~$ wget http://1-2.latest.conquer-on-contact.appspot.com/js/jquery.js
100%[==================>] 57,254 15.0K/s in 3.7s

Does anyone else with a custom domain observe this behavior or do I
have some kind of weird configuration problem?

[Brandon Thomson]

After some additional tests the connection appears to be rate-limited
at 15.0Kb/s on Google's end (I tested from two different broadband
providers, Verizon and Comcast).

[David Wilson]

Hi Brandon,

I quickly checked this, and I'm not seeing the behavior you describe.

It's possible some DNS resolver in between you and the Internet
(perhaps a cheap home DSL router) has cached one set of resolved
addresses for one name, and another set for the other. Perhaps for
whatever reason one of those sets in your case is running slowly?
(maybe they've been recently taken out of service, or enter Google's
network via an interesting route)

Try running nslookup or host from the command line, to see if both
names resolve to ghs.google.com, or the same set of IP addresses.


David

PS: your custom domain is setup to use CNAME ghs.google.com, right?

2009/2/28 Brandon Thomson <gra...@gmail.com>:

>
> After some additional tests the connection appears to be rate-limited
> at 15.0Kb/s on Google's end (I tested from two different broadband
> providers, Verizon and Comcast).
> >
>

--
It is better to be wrong than to be vague.
— Freeman Dyson

[Brandon Thomson]

Thanks very much for the tip, David. I restarted all my networking
equipment and it seems to be working correctly now.

Brandon