High Memory Use With FrontPage Extensions

Featured: Featured Stories | Picture Gallery

Music Books/BottomAd1 | Stretching FAQ B.3 - Groin And Inner-Thigh Stretch

Chat11.com Web Bible11.com MyBibleCenter.com

	The Bush Survival Guide - 250 Ways to Make It Through The NExt Four Years Without Misunderestimating the Dangers Ahead, and Other Subliminable Stategeries
Links: [50 State Center] Hillary's Secret War A People's History Of The United States

High Memory Use With FrontPage Extensions

FrontPage

Subjects > ... > Web > FrontPage

High Memory Use With FrontPage Extensions

Recently, Frontpage extensions on a Windows 2003 computer running IIS 6 was seen using 180MB of ram to update shared borders on large website

• More Information
  • (The site had 43,000+ files, 41,000 of which were in a subdirectory generated by a Perl script. Another copy of the site, on a Linux host with FrontPage extensions, has about 3000 total files, and would occassionally get time out errors on updates of shared borders. Eventually the update, or FrontPage , probably timed out)

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

• More comments on use of SSI and subwebs for large frontpage sites: http://www.webmasterworld.com/forum46/205.htm

Google searches tried for a solution to this problem

• "memory use" "frontpage extensions" "windows 2003" - Nothing
• "memory use" "frontpage extensions" (only 7 results)
  • Great page talking about IIS and PWS: http://archives.hwg.org/hwg-servers/00fa01bf6b3e$aad08580$097c9fd4@gideon
• "large site" "frontpage extensions" (388 results)
  • Most of the articles this returns are ISP's offering hosting
  • List of FrontPage Components: http://www.computertim.com/howto/article.php?topic=frontpage&idn=21
    • Points out that updating shared borders on a large site can take a long time: http://www.computertim.com/howto/article.php?topic=frontpage&idn=28
  • How to choose a webpage editor: http://depts.washington.edu/trio/train/howto/page/editors/index.shtml
  • Great discussion about choosing a webpage editor: http://www.techsoup.org/forums/index.cfm?fuseaction=read&forum=2024&id=51903&cid=117&mid=177982
  • Large thread refering to frustrations in updating 1000 page site in Frontpage: http://www.frontpagetalk.com/forums/m.asp?m=51426&mpage=1&p=1&tmode=1&smode=1&key=
    • Mentions that navigation on a site they are managing is via SSI include file. This person is a newbie, and doesn't realize that doing this is almost mandatory with FrontPage on a large site. Trying to update shared borders, or navigation, on a large site of 200 pages or more, is deadly slow. A FrontPage site that only seems to have 250 pages might actually include 2000 or 3000 files within it's directories, because of the hidden and private information, and graphics files, that FrontPage generates.

For some solutions to problems of managing large sites with FrontPage , please see Handling Large Websites With FrontPage

Check out [Facts About Trees]

Bobsgear - Get A Free Enterrpise Wiki Space!
Review: The Bobsgear Project was started to develop a variety of Confluence plugins. This installation of the Confluence Enterprise wiki includes flexible attachments, many Confluence plugins, personal blogs, interesting articles, and more. Bobsgear already has spaces related to politics, art and photography wiki, technical issues wiki, ediscovery wiki, health, Christian theology and Sabbath School wiki, the bible, book reviews, and quotations. Bobsgear allows free signup, and invites anyone to create a free hosted Confluence wiki space.

NEW USERS CLICK HERE! for a quick introduction to Wiki.

Elapsed:1