FAQ: Performance

[1WSCGomez]

What happens if the service goes down? Will it affect my website?

• The service will not provide any performance or visual impact to your site when the service is not available. The syndication service is a low risk implementation so that if the servers or services were to ever go down, the service will fail gracefully (quietly) and simply return no content. It will not affect the appearance of your website. No Red X's or broken images will be shown. No errors will become visible to the end-customer or client.

What is the response time for ContentCast?

1. At the server stack:
   
   • Script Avg: 123 ms
   • Median: 0 ms for cached responses
     
     
2. Client Side / Network time - this varies based on how much content is returned:
   
   • JavaScript - User Experience Time: Currently averaging under 500ms in the US (145ms - 250ms response time.) That equates to 1/10th of a second.
   • Inline Content Response time: 600ms AVG
   • AVG download time for non-cached inline content only: 2.4s
   • AVG uncached requests - Total Page Load Time: 3.2s
   • AVG cached requests - Total Page Load Time: 1.2s
   • Singe Asset Response Time: 210ms AVG
     
     
3. Logo hovers: Less than 500 ms to serve the hover content but the system currently has an average of 10 ms at the server stack.

The response time will be even faster when the content is smaller or when there is no content to serve for the particular product.

Where are your server stacks located?

• Below is a list of locations for our Application Servers in the Cloud and does NOT include our CDN locations.

  • North America
    • California
    • San Antonio, TX
    • Chicago, IL
    • Virginia
  • Asia
    • Hong Kong, China
    • Singapore
  • Europe
    • Dublin, Ireland
    • Amsterdam, Netherlands
  • Oceania (coming soon)
    • Sydney, New South Wales (coming soon)
    • Melbourne, Victoria (coming soon)

  The CDN (type 1) nodes are located in 24 countries. For Akamai, 127,000 servers As of July 2013

How are your services optimized for maximum performance?

• We use high-availability CDNs such as Akamai.
• Our cloud platform as well as our CDNs have multiple geo locations to ensure the shortest route possible.
• We utilize a search engine index and NoSQL type of environment to eliminate any slow response times from database queries.
• Multiple Cacheing layers are used at:
  1. CDNs
  2. Application
  3. Search engine index
     
     
• Our JavaScript is minified. For example see http://cdn.cs.1worldsync.com/jsc/h1ws.js
• images are cached for 15 mins.
•  

Help! My product page script is slow!

• Follow these steps:

  • Make sure your product page has the div containers properly added. When the containers are missing, your page performance decreases.
    1. Open the product page
    2. Using Chrome, Right click and choose Inspect Element
    3. Click the Console tab
    4. Reload the page.
    5. Make sure you do not see any errors about about "Unable to load content" as shown below (Target element IDs may vary)
       
    6. If you see the above, you will need to do either of the following
       • add the <div id="ccs-explore-product"></div> container to your product pages
       • Disable the block or component that you do not use. Such as Explore Product in the above example.
  • Click the Network tab of the Dev Console and send support the timeline as a screenshot.
  • Send Customer Support a traceroute to ws.cs.1worldsync.com and cdn.cs.1worldsync.com