High Memory Use With FrontPage Extensions
| |
| The Bush Survival Guide - 250 Ways to Make It Through The NExt Four Years Without Misunderestimating the Dangers Ahead, and Other Subliminable Stategeries |
|
Links:
| |
Subjects > ... > Web > FrontPage
Recently, Frontpage extensions on a Windows 2003 computer running IIS 6 was seen using 180MB of ram to update shared borders on large website
FrontPage processes all files in some way when logging in, usually to return a list of the files in the main folder of the site. It also accesses the files of a site in a more extensive way when performing recalculations, and updates of shared components like shared borders and dynamic templates.
Some FAQ's recommend that 50MB of data, and 500 pages is a practical upper limit to the size of a single FrontPage site. Our own experience indicates problems with Unix Hosted FrontPage sites can begin as soon as a site reaches 200+ pages of content, even with FrontPage 2003. (A 350 page FrontPage site can easily have 1700 files and use 350MB of disk space.)
When a site grows to this size, FrontPage may have severe problems with hangs and time-outs. Connectivity problems between your ISP (slow dial-up accounts, or updating FrontPage sites over cellular modem links) can also lead to FrontPage hanging or even timing out. Some FAQs recommend that when this problem starts happening, the content of the site should be organized into subdirectories, and the subdirectories should be turned into "subwebs". This creates a number of smaller subwebs (or child webs) to break your Website up so it does not take FrontPage as long to run through its configuration or recalculation of links. For more information about breaking a site into subwebs with FrontPage , please see Handling Large Websites With FrontPage
For some solutions to problems of managing large sites with FrontPage , please see Handling Large Websites With FrontPage
Check out [Facts About Trees]
|
Interested in Al Jazerra?