<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ancestry.com Blog &#187; Eric Shoup</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/author/eshoup/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Fri, 17 May 2013 00:13:26 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>Ancestry Member Trees Up and Running</title>
		<link>http://blogs.ancestry.com/ancestry/2010/05/20/ancestry-member-trees-up-and-running/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ancestry-member-trees-up-and-running</link>
		<comments>http://blogs.ancestry.com/ancestry/2010/05/20/ancestry-member-trees-up-and-running/#comments</comments>
		<pubDate>Thu, 20 May 2010 06:12:37 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3937</guid>
		<description><![CDATA[It’s been a long day, but I am happy to report the Ancestry Member Trees are now functioning again. As I mentioned earlier, we were making some upgrades in the tree system last night and encountered bugs that took us many hours to work through. Our only solution was to take down the trees to&#8230; <a href="http://blogs.ancestry.com/ancestry/2010/05/20/ancestry-member-trees-up-and-running/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>It’s been a long day, but I am happy to report the Ancestry Member Trees are now functioning again.</p>
<p>As I mentioned earlier, we were making some upgrades in the tree system last night and encountered bugs that took us many hours to work through. Our only solution was to take down the trees to fix the problem. The solution took much longer than we and many of you would have liked, but we believe the problems have been resolved.</p>
<p>If you have problems accessing your family tree on the site, try restarting your browser or clearing your cache. To clear your cache, please see the instructions in the Ancestry.com Help page at <a title="Ancestry.com Help Page" href="http://bit.ly/76G7CA" target="_blank">http://bit.ly/76G7CA</a>.</p>
<p>We truly value your patience as we worked through these issues. Now – happy tree climbing!</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2010/05/20/ancestry-member-trees-up-and-running/feed/</wfw:commentRss>
		<slash:comments>218</slash:comments>
		</item>
		<item>
		<title>Unplanned Maintenance on Ancestry Member Trees</title>
		<link>http://blogs.ancestry.com/ancestry/2010/05/19/unplanned-maintenance-on-ancestry-member-trees/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=unplanned-maintenance-on-ancestry-member-trees</link>
		<comments>http://blogs.ancestry.com/ancestry/2010/05/19/unplanned-maintenance-on-ancestry-member-trees/#comments</comments>
		<pubDate>Wed, 19 May 2010 15:49:29 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3927</guid>
		<description><![CDATA[As an update to our previous post, we want to let you know that we are currently working on unplanned maintenance on the Ancestry Member Trees system. We expect family trees on Ancestry.com and its related international sites to be down for an extended period today. Be assured that the information in your family tree&#8230; <a href="http://blogs.ancestry.com/ancestry/2010/05/19/unplanned-maintenance-on-ancestry-member-trees/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>As an update to our previous post, we want to let you know that we are currently working on unplanned maintenance on the Ancestry Member Trees system. We expect family trees on Ancestry.com and its related international sites to be down for an extended period today.</p>
<p>Be assured that the information in your family tree is safe and will be available when the maintenance is completed. We apologize for any inconvenience this may have caused and will keep you posted.</p>
<p>Thank you for your patience.</p>
<p><span style="text-decoration: underline;"><strong>UPDATE AS OF MAY 19, 2010 AT 12:30 pm MT</strong></span></p>
<p>I wanted to again let everyone know that we are still actively working behind the scenes to get the Ancestry Member Trees system up and running again. Though the trees are not currently available on the site, I wanted to make sure it was clear that searching our historical records collections hasn’t been impacted – so you can search all you want.</p>
<p>I’ll keep you posted as we have more details and appreciate your continued patience.</p>
<p><strong><span style="text-decoration: underline;">UPDATE AS OF MAY 19, 2010 AT 2:30 pm MT</span></strong><strong> </strong></p>
<p>A number of members have asked for more details about the problems we’ve been experiencing today with Ancestry Member Trees.  Unfortunately, as we were doing some big tree system upgrades overnight last night we found some unexpected bugs. We’ve had to take down the trees system to fix the problem.</p>
<p>We do routine maintenance on off-hours to minimize the impact on the time our customers carve out to do family history research. This type of maintenance is generally done behind the scenes to make the site better and usually happens without glitches. This was unfortunately not one of those times.</p>
<p>Based on current estimates, trees will likely continue to be down for the next several hours, at least until sometime later tonight (MT time). Please know that our development and web operations teams are working hard on the problem and we will have it resolved as quickly as we can.<br />
<br />
<strong><span style="text-decoration: underline;">UPDATE AS OF MAY 19, 2010 AT 9:15 pm MT</span></strong></p>
<p>We&#8217;re still working on the issue with Ancestry Member Trees. We will continue working on it into the night and will let you know when we have more news to share.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2010/05/19/unplanned-maintenance-on-ancestry-member-trees/feed/</wfw:commentRss>
		<slash:comments>1576</slash:comments>
		</item>
		<item>
		<title>Site maintenance POSTPONED until Tues Sept 1, 2009, 1 AM MDT</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/26/site-maintenance-postponed-until-tues-sept-1-2009-1-am-mdt/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=site-maintenance-postponed-until-tues-sept-1-2009-1-am-mdt</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/08/26/site-maintenance-postponed-until-tues-sept-1-2009-1-am-mdt/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 00:10:00 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1990</guid>
		<description><![CDATA[I posted yesterday about how we were going to perform some site maintenance on Thursday morning at 1am MDT.  We have postponed this planned site maintenance until next Tuesday, September 1, 2009 at 1am MDT.  We apologize if this change causes you any inconvenience. The Ancestry.com site (and its related Ancestry international sites) will undergo&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/08/26/site-maintenance-postponed-until-tues-sept-1-2009-1-am-mdt/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>I posted yesterday about how we were going to perform some site maintenance on Thursday morning at 1am MDT.  We have <strong>postponed </strong>this planned site maintenance until next <strong>Tuesday, September 1, 2009 at 1am MDT</strong>.  We apologize if this change causes you any inconvenience.</p>
<p>The Ancestry.com site (and its related Ancestry international sites) will undergo scheduled maintenance on Tuesday, September 1, 2009 starting at 1am Mountain Time (7am GMT).  We expect Ancestry.com and its related international sites to be down for about 3 hours.  During this same period, portions of the Rootsweb.com, Genealogy.com, MyFamily.com &amp; familytreemaker.com sites will also be unavailable.  Thanks for your patience as we improve our infrastructure to keep our sites running smoothly.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/08/26/site-maintenance-postponed-until-tues-sept-1-2009-1-am-mdt/feed/</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
		<item>
		<title>Scheduled site maintenance (Thurs August 27 2009, 1-3 AM MDT)</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/25/scheduled-site-maintenance-thurs-august-27-2009-1-3-am-mdt/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=scheduled-site-maintenance-thurs-august-27-2009-1-3-am-mdt</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/08/25/scheduled-site-maintenance-thurs-august-27-2009-1-3-am-mdt/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 23:52:36 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1974</guid>
		<description><![CDATA[We just wanted to let everyone know that the Ancestry.com site (and its related Ancestry international sites) will undergo scheduled maintenance on Thursday, August 27, 2009 starting at 1am Mountain Time (7am GMT).  We expect Ancestry.com and its related international sites to be down for about 3 hours.  During this same period, portions of the&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/08/25/scheduled-site-maintenance-thurs-august-27-2009-1-3-am-mdt/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>We just wanted to let everyone know that the Ancestry.com site (and its related Ancestry international sites) will undergo scheduled maintenance on Thursday, August 27, 2009 starting at 1am Mountain Time (7am GMT).  We expect Ancestry.com and its related international sites to be down for about 3 hours.  During this same period, portions of the Rootsweb.com, Genealogy.com, MyFamily.com &amp; familytreemaker.com sites will also be unavailable.  Thanks for your patience as we improve our infrastructure to keep our sites running smoothly.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/08/25/scheduled-site-maintenance-thurs-august-27-2009-1-3-am-mdt/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Site Maintenance Wednesday morning</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/24/site-maintenance-wednesday-morning/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=site-maintenance-wednesday-morning</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/02/24/site-maintenance-wednesday-morning/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 23:57:54 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Ancestry.com Site]]></category>
		<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/24/site-maintenance-wednesday-morning/</guid>
		<description><![CDATA[The first two parts of our 3-part upgrade of the Member Trees system have completed without requiring any downtime.  As I have mentioned in previous posts, we are spending a lot of effort behind-the-scenes to upgrade this system so that it will continue to meet customer needs as it grows.  As part of this effort,&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/02/24/site-maintenance-wednesday-morning/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">The first two parts of our 3-part upgrade of the Member Trees system have completed without requiring any downtime.  </span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">As I have mentioned in previous posts, we are spending a lot of effort behind-the-scenes to upgrade this system so that it will continue to meet customer needs as it grows.  As part of this effort, we will be upgrading some software on the servers that house this system.  These servers also support Genealogy.com and Rootsweb.com.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">The third and most involved piece of the upgrade will occur early Wednesday morning from <span style="font-weight: bold">12 to 8am MST</span>.  During this part of the upgrade we anticipate the following impacts:<br />
</span></font></p>
<ul>
<li><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">Genealogy.com – Whole site will be down from 12 to 8am MST </span></font></li>
<li><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">Rootsweb.com &amp; Ancestry.com – Rootsweb&#8217;s WorldConnect and its sister database, Ancestry World Tree, will be down from 12 to 8am MST<br />
</span></font></li>
</ul>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">Just to repeat, the outages related to Rootsweb.com and Ancestry.com will be limited to the <span style="font-weight: bold">WorldConnect and Ancestry World Tree systems only</span>.  Ancestry Member Trees (our main tree system) will not be impacted.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p> </o:p>This is part 3 of 3 planned  maintenance windows to complete this upgrade:<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">           Part 1 – Friday, 20  February 2009 – COMPLETE<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p> </o:p>         <strong> </strong>Part 2 &#8211; Tuesday, 24  February 2009 – 12:00 – 8:00 a.m. MST  &#8212; COMPLETE<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">           <span style="font-weight: bold">Part 3 – Wednesday, 25  February 2009 – 12:00 – 8:00 a.m. MST</span><o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p></o:p>Regards<o:p></o:p></span></font></p>
<p><st1:personname w:st="on"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">Eric  Shoup</span></font></st1:personname></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/02/24/site-maintenance-wednesday-morning/feed/</wfw:commentRss>
		<slash:comments>25</slash:comments>
		</item>
		<item>
		<title>Site Maintenance Tuesday morning</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/23/site-maintenance-tuesday-morning/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=site-maintenance-tuesday-morning</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/02/23/site-maintenance-tuesday-morning/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 20:09:07 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Ancestry.com Site]]></category>
		<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/23/site-maintenance-tuesday-morning/</guid>
		<description><![CDATA[The first part of our 3-part upgrade of the Member Trees system completed successfully on Friday without requiring any downtime.  As I mentioned last week, we are spending a lot of effort behind-the-scenes to upgrade this system so that it will continue to meet customer needs as it grows.  As part of this effort, we&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/02/23/site-maintenance-tuesday-morning/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">The first part of our 3-part upgrade of the Member Trees system completed successfully on Friday without requiring any downtime.  </span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">As I mentioned last week, we are spending a lot of effort behind-the-scenes to upgrade this system so that it will continue to meet customer needs as it grows.  As part of this effort, we will be upgrading some software on the servers that house this system.  These servers also support <a href="http://www.ancestry.com/">Genealogy</a> and Rootsweb.</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">We will perform the second part of this upgrade early Tuesday morning from 12 to 8am MST.  We may determine that we need to take down Ancestry.com, Genealogy.com and/or Rootsweb.com <strong>but at this point we do not anticipate having to do so</strong>.  It is possible that during the 3am to 8am MST timeframe on Tuesday you may see some degraded performance of the Trees system.</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial"> This is part 2 of 3 planned maintenance windows to complete this upgrade:</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">           Part 1 – Friday, 20 February 2009 – COMPLETE</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">          <strong> Part 2 &#8211; Tuesday, 24 February 2009 – 12:00 – 8:00 a.m. MST</strong></span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">           Part 3 – Wednesday, 25 February 2009 – 12:00 – 3:00 a.m. MST</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">I will post again to notify you about part 3.</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">Regards</span></span></p>
<p class="MsoNormal"><span style="font-family: Arial;font-size: small"><span style="font-size: 10pt;font-family: Arial">Eric Shoup</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/02/23/site-maintenance-tuesday-morning/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Planned Maintenance this Friday morning</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/19/planned-maintenance-this-friday-morning/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=planned-maintenance-this-friday-morning</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/02/19/planned-maintenance-this-friday-morning/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 23:05:18 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Ancestry.com Site]]></category>
		<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/19/planned-maintenance-this-friday-morning/</guid>
		<description><![CDATA[Our online Member Trees system continues to grow extremely fast.  We are spending a lot of effort behind-the-scenes to upgrade this system so that it will continue to meet customer needs as it grows.  As part of this effort, we will be upgrading some software on the servers that house this system.  These servers also&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/02/19/planned-maintenance-this-friday-morning/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">Our online Member Trees system  continues to grow extremely fast.  We are spending a lot of effort  behind-the-scenes to upgrade this system so that it will continue to meet  customer needs as it grows.  As part of this effort, we will be upgrading some  software on the servers that house this system.  These servers also support  Genealogy.com and Rootsweb.com.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">During the maintenance window we may determine that we need to take down  Ancestry.com, Genealogy.com and/or Rootsweb.com <strong>but at this point we do not anticipate having  to do so</strong>.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p> </o:p>This is part 1 of 3 planned  maintenance windows to complete this upgrade:<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">           Part 1 – Friday, 20  February 2009 – 1:00 – 3:00 a.m. MST<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p> </o:p>          Part 2 &#8211; Tuesday, 24  February 2009 – 12:00 – 3:00 a.m. MST<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">           Part 3 – Wednesday, 25  February 2009 – 12:00 – 3:00 a.m. MST<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">I will post again to notify you of  parts 2 &amp; 3 as we get closer.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p></o:p>Regards<o:p></o:p></span></font></p>
<p class="MsoNormal"><st1:personname w:st="on"><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial">Eric  Shoup</span></font></st1:personname><font size="2" face="Arial"><span style="font-size: 10pt; font-family: Arial"><o:p></o:p></span></font></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/02/19/planned-maintenance-this-friday-morning/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
		<item>
		<title>Site Performance Update</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/06/site-performance-update/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=site-performance-update</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/02/06/site-performance-update/#comments</comments>
		<pubDate>Sat, 07 Feb 2009 00:26:12 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/06/site-performance-update/</guid>
		<description><![CDATA[I wanted to give everyone a quick update on a few of the changes that have been made to improve site performance over the past few weeks.  We recognize we are by no means done.  These represent our first set of improvements: 1. Compression: Across the site we’ve compressed the code that has to be&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/02/06/site-performance-update/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>I wanted to give everyone a quick update on a few of the changes that have been made to improve site performance over the past few weeks.  We recognize we are by no means done.  These represent our first set of improvements:</p>
<p><strong>1. Compression: </strong>Across the site we’ve compressed the code that has to be downloaded with each page.  Our initial tests show that this has reduced “page weights” (or number of bytes you download when you hit a page) by almost 50%.  The improvement is more or less on a given page but it appears to be roughly 50% in aggregate across the site.  We have begun this process with our javascript and stylesheet files.  We are continuing on to our images and HTML files.</p>
<p><strong>2. Photo Serving: </strong>We’ve moved the serving of member-contributed photos to a set of beefier, dedicated servers to ensure this system is getting sufficient resources.  This system comes into play anytime we display member photos like in the pedigree view or on person pages.<br />
<strong><br />
3. Reducing Duplicate Calls: </strong> On a few pages, we have reduced the number of times where key software libraries (code used to construct the site) are downloaded more than once.  Fewer requests to download libraries means faster page load times.  We are working our way through more pages like this on the site.</p>
<p>I&#8217;ll repeat &#8212; we are by no means done.  The Site Performance team is working on a number of further optimizations.  To summarize it, we are working on other ways to reduce the size of the data that is being transferred between us and you and improving our server response time.</p>
<p>We’ll report back as we make further improvements.  Have a good weekend.</p>
<p>regards</p>
<p>Eric Shoup</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/02/06/site-performance-update/feed/</wfw:commentRss>
		<slash:comments>65</slash:comments>
		</item>
		<item>
		<title>Planned Maintenance this Saturday morning (2/7)</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/05/planned-maintenance-this-saturday-morning-27/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=planned-maintenance-this-saturday-morning-27</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/02/05/planned-maintenance-this-saturday-morning-27/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 21:43:44 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Ancestry.com Site]]></category>
		<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/05/planned-maintenance-this-saturday-morning-27/</guid>
		<description><![CDATA[I posted this week about last Saturday&#8217;s planned maintenance and the issues that ensued.  Our data center provider has corrected the problem they experienced last week and will proceed with their planned maintenance this weekend. Maintenance will begin on Friday, 6 February 2009 at midnight (MST) and finish on Saturday, 7 February 2009 at 8:00&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/02/05/planned-maintenance-this-saturday-morning-27/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>I posted this week about last Saturday&#8217;s planned maintenance and the issues that ensued.  Our data center provider has corrected the problem they experienced last week and will proceed with their planned maintenance this weekend.</p>
<p>Maintenance will begin on Friday, 6 February 2009 at midnight (MST) and finish on Saturday, 7 February 2009  at 8:00 a.m (MST).  This maintenance windows is in effect for all Ancestry sites.  Assuming everything goes as planned, <strong>this maintenance should not impact your site experience at all</strong>.  I wanted to let you know this was happening but, again, we do not expect it to impact the operation of any of our Ancestry sites.</p>
<p>regards,</p>
<p>Eric Shoup</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/02/05/planned-maintenance-this-saturday-morning-27/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Site Maintenance last Saturday morning</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/03/site-maintenance-last-saturday-morning/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=site-maintenance-last-saturday-morning</link>
		<comments>http://blogs.ancestry.com/ancestry/2009/02/03/site-maintenance-last-saturday-morning/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 01:48:35 +0000</pubDate>
		<dc:creator>Eric Shoup</dc:creator>
				<category><![CDATA[Ancestry.com Site]]></category>
		<category><![CDATA[Site Status]]></category>

		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/03/site-maintenance-last-saturday-morning/</guid>
		<description><![CDATA[Our data center provider performed routine maintenance on their infrastructure between midnight and 6am Saturday morning.  Due to some unexpected issues that arose related to this maintenance, we took protective actions to take a bank of servers offline.  Other companies hosted in that facility did the same.  As a result, parts of our Ancestry sites&#8230; <a href="http://blogs.ancestry.com/ancestry/2009/02/03/site-maintenance-last-saturday-morning/" class="readmore icon icon-arrow-small">Read more <span></span></a>]]></description>
			<content:encoded><![CDATA[<p>Our data center provider performed routine maintenance on their infrastructure between midnight and 6am Saturday morning.  Due to some unexpected issues that arose related to this maintenance, we took protective actions to take a bank of servers offline.  Other companies hosted in that facility did the same.  As a result, parts of our Ancestry sites were down from 1:05am to 5:45am MST on Saturday morning while the servers were being brought back online.</p>
<p>Sorry for the delay in getting this information out to you as well as any inconvenience this may have caused.</p>
<p>Regards</p>
<p>Eric Shoup<br />
VP Product</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ancestry.com/ancestry/2009/02/03/site-maintenance-last-saturday-morning/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
	</channel>
</rss>
