Hi Kelly! Our WSM has approximately the same magnitude. We have 4 cpu-core´s, 16 GB of RAM and 250 GB harddisk. The required harddisk-size, depends on our project size, amount of files within assetmanagers, ... But this should not be an issue today.
Maybe you are lucky and moving to 11.x (and new hardware) resolves some of your issues. You should be able to use a huge inmemory-pagecache which should improve performance for some scenarios. (we use 8GB inmemory-pagecache which works fine for our projects) But... as tim already said, sometimes there are issue´s within a project. This is nothing we can resolve via a few tips in a blogpost. From my personal view i´ll suggest to first move to 11.x and new hardware. If your issues still exists after this, you´ll need someone how analyses your project(s). Kind regards, Christoph Am Montag, 16. Dezember 2013 20:41:34 UTC+1 schrieb Kelly: > > Hi all - I apologize if this has been asked before- but tried to get the > information from OpenText Support for some time now -- and they keep > routing me to their Consulting team for a (paid) answer which we don't nave > budget for. > Has anyone upgraded from 10.1 to 11.1 and if so, what server config did > you use? I need to requisition a server and I know our current system is > *WEAK*. If we get too many editors on, the whole system pulls to a stop. > Our publishing queue is often going down and requiring rebooting. We're > trying to avoid the same hardware mistakes with new 11.1 install. Any > tips???? > > > *OUR PROJECT* > 130 users but rarely more than 6 or 7 editing at one time. > If we have over 10 users editing at one time, editing and publishing slow > to a crawl, SmartEdit WYSIWYG Editors just 'hang' frozen. > Also publishing stops responding and all the server pub jobs just 'pile > up' in the DB until rebooted. > > Our project is one Main Website with 80 separate micro-sites inside it (I > know, I know! It was NOT set up by me) > When I run our 3x week "Publish All Pages" job, about 40,000 pages get > pumped out. The publishing process takes a bit over 10 hours and can > (obviously) only be run after hours. > OpenText Support suggested we restart all 3 servers *weekly* due to some > "memory leak" issue that kept happening on cms editing servers - which > disconnected our CMS servers from the DB and losing content. > > > > *CURRENT SERVER CONFIG* > Single Processor: Intel Xeon CPU E5-4640 0 @ 2.40 GHz 2.19 GHz > 4 GB RAM > 80 GB hard drive > 2 clustered cms editing servers - with a load balancer in front > 1 cms publishing server that takes it orders from the 2 editing servers > > > > *O/S and DB* > WMS 10.2 SP2 > Windows Server 2008 R2 Enterprise (sp1) > SQL 2008 R2 > IIS 7/8 > > > > > > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
