Yes I've noticed the same thing but I'm using uSiteBuilderAdmin to conrtol when to sync and when I use it to manually sync it takes up to 2 minutes for a pretty small site.  Good catch on the umbracolog entries - their timestamps seem to be in line with the amount of time it is taking for the manual sync.

If you want to supress at startup I think you have the wrong appKey as startup is fine for me - try this slightly different one (no double p in Supress):

siteBuilderSupressSynchronization

Regards,
Matt 

I researched this a little more and cut my manual sync time down from 2 minutes to 6 seconds for 27 documentTypes - this is when there were no changes to any of the documentTypes though - that 6 seconds will go up for each change detected - if you grab the MVC source of uSiteBuilder (Feb 4 release) and modify the culprits are the following lines.  Here's a link to the MVC version:
http://usitebuilder.codeplex.com/SourceControl/network/forks/StephenWRogers/uSiteBuilder?branch=MVC ;

DocumentTypeBuilder\DocumentTypeManager.cs - line 248'ish

Change from:

docType.Text = docTypeName;
docType.Alias = docTypeAlias;
docType.IconUrl = docTypeAttr.IconUrl;
docType.Thumbnail = docTypeAttr.Thumbnail;
docType.Description = docTypeAttr.Description;

to:

if (docType.Text != docTypeName)
docType.Text = docTypeName;
if (docType.Alias != docTypeAlias)
docType.Alias = docTypeAlias;
if (docType.IconUrl != docTypeAttr.IconUrl)
docType.IconUrl = docTypeAttr.IconUrl;
if (docType.Thumbnail != docTypeAttr.Thumbnail)
docType.Thumbnail = docTypeAttr.Thumbnail;
if (docType.Description != docTypeAttr.Description)
docType.Description = docTypeAttr.Description;

And then in ManagerBase.cs on line 209'ish change:

contentType.SetTabOnPropertyType(property, tabId);

to

if (property.TabId != tabId)
contentType.SetTabOnPropertyType(property, tabId);

I'm assuming the above has something to do with the new .Save() functionality in v6 still doing a Save even though nothing has changed?

HTH.

Regards,
Matt 

This is going to be related to this: http://issues.umbraco.org/issue/U4-1714 - there should be a fix in 6.0.1

Stephen

is working on a reply...