Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Why your CMS is slow

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends


Report Excerpt

The Web CMS Report 2009 looks at... Serena Collage

"Entitlements management is a bit primitive and may not scale well for highly distributed contributor models. The product has groups, but no real notion of roles. Groups cannot be nested, but users can belong to more than one group. "

(p. 444)

More about The Web CMS Report 2009

Our customers say

"The Web CMS Report was the roadmap for our entire CMS selection process. It truly provided a basis for understanding what we should look for and expect in a CMS. Above all, since we used the report as our guide, we are more-than-confident in our CMS selection. If we had to go through the process all over again, we'd still rely as heavily on this report as the first time.
- - Michele McDonald,
IT Project Manager, University of Oklahoma

NEW at CMS Watch

The Web CMS Report 2009 The Web CMS Report 2009: In its 15th edition, this report evaluates 42 web content management systems and vendors... Read more
The ECM Suites Report 2009 The ECM Suites Report 2009: This report evaluates 30 ECM offerings... Read more
Technology Transfer in Rome Join us in Rome: On November 6-7 in Rome, CMS Watch's Theresa Regli will teach a tutorial on "Enterprise Search Technology and How to Optimize It"... Read more

 

TrendWatch Blog

Why your CMS is slow

27-Jan-2007

MindTree Consulting's Pranshu Jain offers 8 reasons why a CMS might be frustratingly sluggish for content contributors. To his excellent compendium, I'll add a few more:

  1. Voluminous client-side code in the contributor UI
  2. Delays in content publish/push to staging or preview servers
  3. Simple lack of sufficient hardware and network resources
(As an aside, I had the pleasure of meeting Jain in Denmark, and regret only catching up to his blog now; if you care about Web architectures, it's highly nutritious reading.) Via Apoorv Durga.

- Submitted by: Tony Byrne, Analyst

All CMS Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.



What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048