Looking at the CMS log viewer - and comparing this when the site went slow (server peaking at 100%) - the is a Umbraco event just before the spike - Umbraco.Cms.Core.Runtime.MainDom. Is this a bug - or is there a fix or can anyone share any information regarding Umbraco.Cms.Core.Runtime.MainDom

@jonroberts we are also facing the same issue , did you get a solution on this?

No - nobody replied

How is MainDom configured? Database? And how is it hosted? And is it multi-instance (i.e., "load-balanced")? > Available options: > > "FileSystemMainDomLock"- Available cross-platform, uses lock files written to LocalTempPath to control acquisition of MainDom status. > > "MainDomSemaphoreLock" - Windows only, uses a named system Semaphore with a maximumCount of 1 to control acquisition of MainDom status. > > "SqlMainDomLock" - Available cross-platform, uses the database to control acquisition of MainDom status. > > The default implementation unless configured otherwise is FileSystemMainDomLock.