Hi vwd,

The team are still going through the process of deciding which CMS to use. What would stack the chips in Silverstripes favour is if someone from the SS Development team would confirm whether Silverstripe would cope with an 18,000 page website. An existing website of similar size, as an example, would also be beneficial in swaying people in the team to choose Silverstripe.

Cheers
Snarf1974

Hi Snarf,

The larget site we have build has about 6,000 pages, it's an intranet for the Moving Picture Company (MPC) managed by 500 odd employees and SilverStripe holds up just fine. That is as long as you can handle having that size of site tree, which obviously can get quite unwieldy. That site also has *thousands* of files, although we are using the TinyMCE image file/manager instead of the build in SS aset manager as the primary file uploader/manager. However if you are using a modern browser in your org then you might also look at Kick Assets which has some awsome HTML5 file features: http://www.leftandmain.com/silverstripe-screencasts/2011/08/25/introducing-kickassets-give-assetadmin-the-boot/

Also for a large tree this snippet is indispensable: http://www.ssbits.com/snippets/2011/making-the-tree-tools-sticky/

I also guess it depends on the type of content you want on the pages, if you have hundreds/thousands of 'pages' all under the same parent then you would be better off using the techniques mentioned by swaiba to make DataObjects behave like pages managed via ModelAdmin. We are very close to releasing a module that should make this process super easy :)

In terms of the Multisite module, it is a pretty good starting point for multi-site management, giving you a nice site switcher and tree per site, but it is limited in terms of sharing content between sites, as Swaiba mentioned we had to do some pretty extensive development to male it work for our client.

Anyway if you have any more questions just let me know :)

Aram

Snarf,

We have several large SilverStripe installs, one with around 100,000 pages. It's not quick but not many CMS's would be quick with this many pages. It's usable though especially if you cache aggressively and have a powerful dev machine and server.

Tricks to speed up larger SS sites are to:

1. Disable the function get_homepage_link (which mostly needlessly searches and file sorts SiteTree for every row in the table)
2. Keep custom page types / decorators to a minimum
3. Use custom queries when the ORM gets too expensive (use a dbprofiler or similar to determine which ones).

optional:
4. Watch the movie "Cache Me if You Can" like 10 times and take notes.
5. Sacrifice your first-born child to Baal, one of the seven princes of Hell.