Today, I got the first performance feedback from our technology preview partners. Some partners who tested with big projects that had caused some headaches in the past, where quite excited about the performance. While doing a publication, the cpu usage climbed up to 90 %, memory was filled and working in SmartEdit was possible with a very good performance.
Maybe some of the partners who tested this could step up the plate and give more insights on their performance measures.
Some insides about the technology preview VMware:
We delivered a VM based on Windows Server 2008 x64 with 4 GB of ram, using 2 CPUs. For sure, it is possible that partners with adequate hardware could change the settings and test with even better hardware.
Hello,
AntwortenLöschenthis is a very interesting and very encouraging message. We are running a large MS 10.1 application (80,000 pages in 2 languages) at Transport Canada and indeed experiencing some performance problem. We are using Oracle 11g as our database.
I am wondering if you have any of your testing partners running MS 11 with Oracle, and if yes, what is their feedback about Oracle performance?
Thank you,
Irina Krasteleva
irina.krasteleva@tc.gc.ca
Hi Irina,
AntwortenLöschenthe Technology Preview of version 11 did not have support for Oracle. Thus, we currently do not have any feedback from partners regarding Oracle support.
We are currently in the process of finishing the version. As far as I know, we will do a second preview that is very similar to the final version and it will certainly contain Oracle support.
Hi Dennis,
AntwortenLöscheni saw the webinar of WSM11 last week and Frank Steffen told that he used a virtual maschine with 2 cpu's and 4 gb ram. I this case he was able the use WSM11 with only 1 editor. He also said that the system normaly needs 4 cpu's and 8 gb ram as a minimum requirement. What is your experience on this? Currently it seems that WSM will be a performance eater.
regards
Patrick
Hi Patrick,
AntwortenLöschensorry, for my late response, but we have been very busy finishing version 11.0.
I don't think, version 11.0 is a performance eater. We're experiencing a far better throughput than older versions of WSM. We now configured the ServerService that contains the PageBuilder and the ObjectProcessService that runs the RenderTag and Navigation processes to each use up to 2.5 GB of memory. As we do have some additional smaller processes and the operating system itself, we recommend 8GB RAM as minimum. We also think that 8 GB and Quadcore is quite normal today.
Everything below this configuration can only be considered as a developer setting and this was what Frank intended to say. If you need a developing environment of WSM, you could use a smaller configuration, but in production systems, 8GB+ and Quadcore is the minimum.
Regards,
Dennis