Theoretically, you can have up to 4 billions for all versions, so if each page has 10 versions, you can have up to 400 million, given or take. That's a hard limit but I don't think there is any site reached that number.

I think we have some customers with more than 1.5 million of pages. So with properly configuration and optimization, a couple of million would be achievable.

/Q

Thank you.  I would hope that we'd never have that many pages!

Karen

For a site with 17,000+ Pages, lots of Dynamic Content and Composer Blocks, would you expect to need to increase the timeout in the web.config file to cope with larger amounts of data?

Thanks

Karen

No, I would expect that to be the last thing to touch.

I don't know about "lots of", but if your site has big enough data, then you should scale the hardware. 

If the hardware is good enough but the site is still slow then try some profilers to find the bottleneck - database, network, some bad written code,...?

Increasing timeout setting can be the solution in some edge case, but for daily uses I don't think you'll need it.

Regards,

/Q

Thanks again.  That's really helpful.

Regards

Karen