I'm not sure where to begin looking, I'm working on a custom examine indexer, which may be related or not... so I deleted all the Index and Search providers, and I get the same issue.
The async logger runs on a dedicated thread, hence the thread sleep. It does not interact with any other thread so that is not your issue.
Not sure what the 2nd one is but just looks to be .Net doing some stuff.
The third one has more information about publishing.... but doesn't really tell us much.
How are you publishing ? the 3rd trace shows: umbraco_dialogs_publish_aspx ... so are you publishing via the dialog? And what options are you choosing ? Does the process actually complete after a few minutes and anything show up in your logs that are alarming ? Is it for every single page you try to publish, etc...
Also, how much data do you have in your install ? If you delete the indexes then Examine will rebuild them when it detects they don't exist... this can take a considerable amount of time to gather all of the data depending on how much data you have in your install.
Oh yea, I tried publishing in various ways (from dialog. and unpublishing etc.)
It seems to be the first publish (unpublish) that is really slow, then it's fast. untill I re-load the app (touch web.config etc)
The Examine Indexes Folder is 93MB (the default External folder is 33MB, and the umbraco.config file is 28MB )
I get the slow load for every page I've tried, I tried various doc types.
If I delete logs, and examine indexes, and recycle the app pool, and check inside the fresh log I get the following (see below)
I started the site, it built the index, the first publish took about 6 minutes.
the second publish was very quick.
I touched the web.config and published again it's now taking aages (time=14:20 I assume it'll finish in 6 minutes)
oh here's the log (not v. interetsing)
2013-05-14 13:50:48,198 [5] INFO Umbraco.Core.CoreBootManager - [Thread 1] Umbraco application starting
2013-05-14 13:50:48,214 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Determining hash of code files on disk
2013-05-14 13:50:48,217 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Hash determined (took 3ms)
2013-05-14 13:50:48,570 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter, found 0 (took 347ms)
2013-05-14 13:50:48,577 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Web.Mvc.SurfaceController, found 0 (took 4ms)
2013-05-14 13:50:48,586 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.Media.IThumbnailProvider, found 3 (took 4ms)
2013-05-14 13:50:48,590 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.Media.IImageUrlProvider, found 1 (took 4ms)
2013-05-14 13:50:48,597 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of umbraco.interfaces.IApplicationStartupHandler, found 12 (took 4ms)
2013-05-14 13:50:48,618 [5] INFO Umbraco.Core.CoreBootManager - [Thread 1] Umbraco application startup complete (took 417ms)
2013-05-14 13:50:50,668 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of umbraco.interfaces.IDataType, found 42 (took 4ms)
2013-05-14 13:50:50,677 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of umbraco.interfaces.ITree, found 38 (took 4ms)
2013-05-14 13:55:05,707 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of umbraco.interfaces.IApplication, found 7 (took 9ms)
2013-05-14 13:55:05,717 [5] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of umbraco.interfaces.ITree, found 27 (took 5ms)
2013-05-14 13:55:08,138 [5] INFO Umbraco.Core.PluginManager - [Thread 17] Completed resolution of types of umbraco.XsltExtensionAttribute, found 0 (took 20ms)
2013-05-14 13:55:18,552 [5] INFO Umbraco.Core.PluginManager - [Thread 12] Completed resolution of types of umbraco.BusinessLogic.Actions.IActionHandler, found 1 (took 4ms)
2013-05-14 14:20:07,593 [5] INFO Umbraco.Web.UmbracoApplication - [Thread 55] Application shutdown. Reason: ConfigurationChange
2013-05-14 14:20:09,375 [62] INFO Umbraco.Core.CoreBootManager - [Thread 26] Umbraco application starting
2013-05-14 14:20:09,390 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Determining hash of code files on disk
2013-05-14 14:20:09,393 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Hash determined (took 3ms)
2013-05-14 14:20:09,749 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter, found 0 (took 350ms)
2013-05-14 14:20:09,755 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of Umbraco.Web.Mvc.SurfaceController, found 0 (took 4ms)
2013-05-14 14:20:09,761 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of Umbraco.Core.Media.IThumbnailProvider, found 3 (took 4ms)
2013-05-14 14:20:09,765 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of Umbraco.Core.Media.IImageUrlProvider, found 1 (took 3ms)
2013-05-14 14:20:09,771 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of umbraco.interfaces.IApplicationStartupHandler, found 12 (took 3ms)
2013-05-14 14:20:09,791 [62] INFO Umbraco.Core.CoreBootManager - [Thread 26] Umbraco application startup complete (took 413ms)
2013-05-14 14:20:09,855 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of umbraco.interfaces.IApplication, found 7 (took 5ms)
2013-05-14 14:20:09,867 [62] INFO Umbraco.Core.PluginManager - [Thread 26] Completed resolution of types of umbraco.interfaces.ITree, found 27 (took 4ms)
2013-05-14 14:20:12,082 [62] INFO Umbraco.Core.PluginManager - [Thread 53] Completed resolution of types of umbraco.interfaces.IDataType, found 42 (took 4ms)
2013-05-14 14:20:12,089 [62] INFO Umbraco.Core.PluginManager - [Thread 53] Completed resolution of types of umbraco.interfaces.ITree, found 38 (took 3ms)
2013-05-14 14:20:12,987 [62] INFO Umbraco.Core.PluginManager - [Thread 53] Completed resolution of types of umbraco.BusinessLogic.Actions.IActionHandler, found 1 (took 9ms)
2013-05-14 14:20:30,198 [62] INFO Umbraco.Core.PluginManager - [Thread 46] Completed resolution of types of umbraco.XsltExtensionAttribute, found 0 (took 18ms)
Rebuilding indexes will take quite a while but if the indexes are missing during application startup the examine will try to rebuild them during startup (you can disable that in config though) http://our.umbraco.org/documentation/Reference/Searching/Examine/full-configuration "RebuildOnAppStartup". Once the indexes are there though, Examine just re-indexes the individual nodes and indexing is run async (unless you've disabled that) so you wouldn't really be waiting for that anyways.
It does seem real strange though and I don't really think it's an Examine issue since your indexes are building no problem. Might be best to get the source and debug at the methods:
[In a sleep, wait,or join] > mscorlib.dll!System.Threading.Monitor.Enter(object obj,refbool lockTaken)+0x14 bytes umbraco.DLL!umbraco.content.UpdateDocumentCache(umbraco.cms.businesslogic.web.Document d ={umbraco.cms.businesslogic.web.Document})+0x66 bytes umbraco.DLL!umbraco.library.UpdateDocumentCache(umbraco.cms.businesslogic.web.Document doc)+0x75 bytes
Also, I think you forgot to post the info from your log.
I've seen a similar issue in 6.1 - the first publish takes forever, but subsequent publishes are super speedy. My times aren't quite as bad as Murray's (about 10 seconds), but still definitely noticable.
I just ran a test in order to check out my log file, and I noticed a bunch of SitemapProvider errors on nodes that I wasn't publishing. So I tried commenting out the <siteMap> section of the web.config, and now the first publish is super speedy again! Murray, want to give that a shot?
Nice! So its the sitemap provider. This was always enabled (or should have been) previous to 4.11.8... Maybe something has changed to actually make it work now :) TBH I've never used a sitemap provider for anything, it's probably worth investigating how it is currently implemented and who uses it. I can assume that it might not be working the way a sitemap provider was intended to work.
Sleeping on the job
Hi all
I have a site I've upgraded from umbraco 4.0.3 to 4.11.8 (I don't know if that's relevant)
When I publish something it takes a very long time. (many minutes.)
If I pause the process I see this call stack:
or
I'm not sure where to begin looking, I'm working on a custom examine indexer, which may be related or not... so I deleted all the Index and Search providers, and I get the same issue.
The async logger runs on a dedicated thread, hence the thread sleep. It does not interact with any other thread so that is not your issue.
Not sure what the 2nd one is but just looks to be .Net doing some stuff.
The third one has more information about publishing.... but doesn't really tell us much.
How are you publishing ? the 3rd trace shows: umbraco_dialogs_publish_aspx ... so are you publishing via the dialog? And what options are you choosing ? Does the process actually complete after a few minutes and anything show up in your logs that are alarming ? Is it for every single page you try to publish, etc...
Also, how much data do you have in your install ? If you delete the indexes then Examine will rebuild them when it detects they don't exist... this can take a considerable amount of time to gather all of the data depending on how much data you have in your install.
Oh yea, I tried publishing in various ways (from dialog. and unpublishing etc.)
It seems to be the first publish (unpublish) that is really slow, then it's fast. untill I re-load the app (touch web.config etc)
The Examine Indexes Folder is 93MB (the default External folder is 33MB, and the umbraco.config file is 28MB )
I get the slow load for every page I've tried, I tried various doc types.
If I delete logs, and examine indexes, and recycle the app pool, and check inside the fresh log I get the following (see below)
I started the site, it built the index, the first publish took about 6 minutes.
the second publish was very quick.
I touched the web.config and published again it's now taking aages (time=14:20 I assume it'll finish in 6 minutes)
oh here's the log (not v. interetsing)
Well, that is a extremely large amount of data :)
Rebuilding indexes will take quite a while but if the indexes are missing during application startup the examine will try to rebuild them during startup (you can disable that in config though) http://our.umbraco.org/documentation/Reference/Searching/Examine/full-configuration "RebuildOnAppStartup". Once the indexes are there though, Examine just re-indexes the individual nodes and indexing is run async (unless you've disabled that) so you wouldn't really be waiting for that anyways.
It does seem real strange though and I don't really think it's an Examine issue since your indexes are building no problem. Might be best to get the source and debug at the methods:
Also, I think you forgot to post the info from your log.
Doh... sorry now the log info shows up :)
Yea, I'm guessing it's not examine, cos as I mentioned, I tried deleting all the Index and Search providers, and I get the same issue
I've seen a similar issue in 6.1 - the first publish takes forever, but subsequent publishes are super speedy. My times aren't quite as bad as Murray's (about 10 seconds), but still definitely noticable.
I just ran a test in order to check out my log file, and I noticed a bunch of SitemapProvider errors on nodes that I wasn't publishing. So I tried commenting out the <siteMap> section of the web.config, and now the first publish is super speedy again! Murray, want to give that a shot?
-Tom
Wow, yep, that sorted that out. super crazy! (NB: internalIndexer counts 8628 documents)
Nice! So its the sitemap provider. This was always enabled (or should have been) previous to 4.11.8... Maybe something has changed to actually make it work now :) TBH I've never used a sitemap provider for anything, it's probably worth investigating how it is currently implemented and who uses it. I can assume that it might not be working the way a sitemap provider was intended to work.
We weren't using it.
The web config for it was the same in 4.03 before we upgraded so... perhaps it did start working in some version albiet very slowly
is working on a reply...