#179 - Some early results and questions on the All Tribes deployment...Below I have three results, the first is All Tribes on their existing
hosting infrastructure with a balancer in front but no Accelerator and
their old AWS backend. The second is the impact of our hosting and
Accelerator code (new backend, new accelerator configured). And the third
is direct to the new All Tribes backend.
There are a few things that I can't explain in these results. The only that
I am hung up on is why the new backend is in the IAD data center while the
brokers are in DFW and ORD? Obviously, because the webpagetest region is
also set to the Dulles, VA region the direct to the backend result is
actually pretty good. Better than I would have expected. This begs the
question why the backend is not also in DFW next to the shared Brokers that
we are using?
Any thoughts on whether this is a good or a bad thing?
My inclination would be to place the backend in either ORD or DFW so we
don't need most of the Rackspace data centers to be operational for this
site to function :)
The other result I can't explain is the load times for the all us solution.
There are some external links that take forever that don't impact the site
visually. The old site through us has no issue and the new backend has no
issue. Not a big deal just sort of strange.
JD - Let's send the test email to the customer as soon as we can.
Preferably tonight. I am ready to have this one behind us and in
production.
Thanks for all of your efforts here everyone. I think they will be psyched
on the performance that we are delivering for them.
Jay
All Tribes before Lagrange Hosting and our Accelerator.
[image: Inline image 1]
All Tribes with Lagrange Hosting and our Accelerator.
[image: Inline image 2]
Direct to the All Tribes backend.
[image: Inline image 3]
----
Jay Smith, Ph.D.
cell: (720) 839-5378
www.lagrangesystems.com
