Make sure you clear out cache files regularly. This should include ASP.NET cache directories, particularly if you are using ASPX for pre- execute or RDExecute.
Our publishing went from 1 hour to 13 in the space of a few days! Turns out we had **1 MILLION** temp files in the ASP.NET temp directory - took me 4 hours to delete them!! I've never seen anything like it before. Normally they go here: C:\Windows\Microsoft.Net\Framework\v2.0.50727\ASP.NET Temporary Files You will need to stop the IIS App Pools to delete the files out. Also check out my article on tuning the pagebuilder services on the blog at http://www.reddotcmsblog.com/performance-tuning-parameters-for-navigation-manager (note that NavMgr and PageBuilder share their memory services). HTH. Regards, Richard Hauer ==================== 5 Limes Pty Limited www.5Limes.com.au On Oct 18, 6:35 pm, dylanr <[email protected]> wrote: > Has anybody experienced a performance decrease following the > installation of SP1? > > The nightly full-site publish used to take 1 hour to complete, but > after installing SP1 it takes 2-3 hours. A PDF publish of 370 pages > used to take 10 minutes, but now takes 2.5 minutes per page. When > looking at the PageCache.log file, it looks like the cache is being > dumped several times during publishing: > > Wait execute cache action=freememory, > Threadguid:DBD8D9F5076A4297930F6B928EE45E13, Thread count=1 > Execute cache action=freememory, > Threadguid:DBD8D9F5076A4297930F6B928EE45E13 > Delete memory: MemorySize:1117626368, TotalMemory allocated:964206964 > Memorysize increased: MemorySize:173109248, TotalMemory allocated: > 15048960 > > Occurrences of the snippet above with 'action=freememory' only started > following the upgrade. > > On Oct 1, 10:03 am, El Pollo Loco <[email protected]> wrote: > > > > > The new pagebuilder just allows more things to occur at the same time. > > So in those instances where multiple publications or heavy > > asynchronous tasks would slow down the CMS, this it not the case > > anymore. > > > I know that the plan was to develop a new pagebuilder in .Net, but at > > a certain point they realized this was too much of an effort. Redoing > > the OR mapping and other things would have taken too much time. > > > I think there were new tools or functionality available with .NET 3.5 > > that allowed Nick and those guys to port the old VB version of the > > pagebuilder to .net 3.5 to take advantage of some of the benefits > > of .Net. Something to do with the variant data type and enhancements > > with .Net 3.5. > > > An interesting article here about the future of reddot > > here:http://www.opentext.com/2/global/press-release-details.html?id=2247 > > > There was going to be a MS11, but per the above link, this will no > > longer happen. > > > On Oct 1, 5:05 am, "Richard Hauer (5 Limes)" <[email protected]> > > wrote: > > > > We have discovered that the pagebuilder has a bug with LiveServer > > > Constraint placeholders, in that you can't put one into the template > > > because there is some dubious late-bound code that was automatically > > > upgraded by Visual Studio from VB to VB.Net, badly, and now doesn't > > > render. The late-boundness means the code compiles but goes to > > > exception at run-time. Awesome! > > > > The element can exist on the template but it's rendered useless by the > > > bug as you can't include it in the output. > > > > We have an open ticket with OT - they have told us to wait for v11 > > > (but will probably fix it sooner once people start to complain). > > > > HTH. > > > > Regards, > > > Richard Hauer > > > ==================== > > > 5 Limes Pty Limitedwww.5Limes.com.au > > > > On Oct 1, 10:35 am, markus giesen <[email protected]> wrote: > > > > > The CSS and Javascript issue is only related to the new UI introduced > > > > with version 10 > > > > > What happens here is: > > > > The CSS is affected by your projects styles, so your styles might make > > > > your HTML cutup to overlay the interface. > > > > Mitigation: Reqrite and tweak your CSS, this is at the moment not a > > > > proper solution and a hotfix would be nice to have soon. > > > > > The JS - It uses the Microsoft JS framework (for AJAX&others) and > > > > depending on the way you use other javascript frameworks or your own > > > > script this might break if your code throws errors or interferes with > > > > the RDJS > > > > > So the answer for your question is: NO this version 9 update doesn't > > > > come with the new UI issues of v10. > > > > (Don't know about any others though) > > > > > I am keen to move and develop my project on version 10 soon and hope > > > > OpenText will come up with a solution soon. > > > > > On 1 Okt., 03:01, cburne <[email protected]> wrote: > > > > > > Not sure. I haven't tested it well enough yet :) I haven't even > > > > > really tested it to verify the performance improvement in > > > > > PageBuilder. I will post as I continue testing... > > > > > > On Sep 30, 6:34 am, Joshua Ellis <[email protected]> wrote: > > > > > > > On Sep 30, 2:50 am, cburne <[email protected]> wrote: > > > > > > > > Found out some good news recently that I thought I'd share. SP1 > > > > > > > came > > > > > > > out a few weeks ago. > > > > > > > The blog posting says that SP1 includes the .Net-erific pagebuilder > > > > > > that is part of OTWCMS 10. Does it also include the problems with > > > > > > CSS > > > > > > and PreExecute code that some folks have reported with v10? Not > > > > > > trying > > > > > > to be snarky... we've been burned by RedDot service packs before.- > > > > > > Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
