2 New Data Centers Bring Faster Global Page Load Times
Page load times have just improved in Australia/New Zealand and Europe, thanks to two new data centers added to Adobe’s growing network of data collection nodes. This brings the total number of regional data collection (RDC) nodes to 10, including:
- San Jose, California
- Dallas, Texas
- Ashburn, Virginia
- Tokyo, Japan
- Sao Paulo, Brazil
- Singapore
- Hong Kong, China
- London, England
- Amsterdam, The Netherlands (new)
- Sydney, Australia (new)
Beginning immediately, if you have RDC-enabled data collection (data is being sent to omtrdc.net) all visitors to non-SSL pages will be automatically routed to the nearest data center. No change is required on your part.
Target users should be aware that these two new data centers support Target Edge functionality. And the Amsterdam data center also supports Media Optimizer Ad Pixel/RTB services.
For those of you who are curious about RDC and these data centers in general, here is an overview.
Q. What is RDC?
A. Regional Data Collection. This feature ensures site visitors are hitting the nearest data collection center, thus reducing page load time. We have regional data collection centers in San Jose, Dallas, Virginia, London, Tokyo, Singapore, Brazil, Hong Kong, and now Sydney and Amsterdam. For more details on Regional Data Collection, see this post.
Q. How much will this change improve overall page load time?
A. Browsers request multiple pieces of content at once whenever they can. Most pages download dozens of pieces of content, so this change is unlikely to double your page load speed. However, if you have an otherwise snappy page, a change like this should be noticeable to site visitors.
Q. How can I tell if I’m using RDC-enabled data collection?
A. Find your data collection domain. If it ends with omtrdc.net, you’re on RDC. If your collection domain ends with you’re own domain, you need to ping it to see if it’s mapped to omtrdc.net or 2o7.net (non-RDC). Here’s how to find your data collection domain in Chrome (there are a few other ways).
1. Go to your web site in Chrome and then go to Chrome Menu > Tools > JavaScript Console.
https://blog.adobe.com/media_e9b55eee4fec8bc5e0c128c5c34a907993bd6587.gif
2. With the Console tab selected, type s.trackingServer and hit Enter.
https://blog.adobe.com/media_d81d4fe9dabafb957b2a5efe8fbd4361fe987c6c.gif
https://blog.adobe.com/media_c9b36dcf738936968ea59421b4acfeb0d39af01b.gif
3. What you see is the data collection domain used on your site. If this ends in omtrdc.net, you’re on RDC. If this is your domain, as shown here, open a Command Prompt (Windows) or Terminal (Mac) and type “ping [your collection domain]”. If it ends with omtrdc.net, you’re on RDC. If it ends in 2o7.net, you’re not.
https://blog.adobe.com/media_9241721230ed51d3a1a423eb2c612fd3e9d4c6f0.gif
Q. How do I start using RDC?
A. Instructions for migrating to RDC are found in SiteCatalyst Help. Go to SiteCatalyst > Help > Help Home and type Transitioning to RDC for detailed instructions.
**Q. **Will RDC improve report speed or just data collection speed?
A. Report speed is not affected by regional data collection, it simply improves response times for your visitors.
Q. Can I license my SSL certificate for fewer servers and have it installed in just the America’s, or just Europe, since most of my traffic is in one place?
A. No, selective deployments of SSL certificates are not supported.