On Sunday 03 June 2007 08:22:10 Tim Chase wrote: > Just as a side note, I believe Akami does geographic cache > controlling in addition to simply caching out of a central > location (as do several other big names in the caching business). > This means that users in, say, China, hit the cache controlling > machines in China, rather than your central servers in, say, > Atlanta. If all your users are fairly geographically > centralized, this may not introduce noticeable problems.
The users of this site will be almost exclusively in the U.S. The site is for one of those high-profile American talk shows that wouldn't really appeal to those outside the States and perhaps Canada. > However, if your user-base is spread across the globe, a > centralized solution out of a single data-center may introduce > latency problems for more distant users. Some companies > (salesforce.com, for example) have several data-centers, > geographically dispersed so that customers end up hitting the > closest one. Perhaps Akami has reports that can be generated > from their usage to provide management with the data needed to > decide whether users are clustered near your data-center (such as > on the same continent), or if they're all around the world. I'm assuming that the very large sites using memcached are themselves geographically dispersed. LiveJournal, FaceBook, Wikipedia - I'm wondering if they have their own data centres. It's still worth getting stats from Akami if I can, however. It could give me a good idea as to where to host the site if I know where the biggest concentration of "viewers" is. Thanks again, Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
