If you’re like me, a considerable amount of your computing experience takes place within Firefox.\u00a0 I have a couple of old, slow computers, however, for which the actual loading speed of Firefox itself is problematic.\u00a0 Either can keep up fine with web content, and their connections are fast, but Firefox itself can take a surprisingly long amount of time to come up\u00a0 — which is inevitably when I need it.\u00a0 Leaving Firefox open but minimized is a somewhat reasonable solution, except for Murphy’s law, which is strictly enforced here, means that I need Firefox after having just booted the machine, or just closed it without thinking.<\/p>\n
XP has a strategy for speeding the load time of any<\/em> application, which is known as “prefetching.”\u00a0 There are a lot of myths and misinformation about what this is, but essentially, XP keeps track of how a program is loaded, and stores this information in its prefetch area.\u00a0 Next time the same program is launched, XP consults the prefetch area to see how to load the program optimally.<\/p>\n N.B.:\u00a0 XP prefetching is automatic<\/em> and works for every application<\/em>.\u00a0 There’s a myth that adding “\/prefetch:1” (or some other number) switches to the end of your program’s launch criteria will do something beneficial with the prefetch subsystem.\u00a0 It does do something<\/em>, and that is to pass the number to the hash used for prefetching.\u00a0 So adding it will have the effect of first slowing down the launching of Firefox to its unprefetched speed, then the next time it’s launched, it will be as fast as it was before the switch was added.\u00a0 Naturally, adding this switch is simply a waste of time.<\/p>\n While I’m digressing, I should point out that clearing the prefetch folder is an equally pointless waste of time and resources.\u00a0 Getting rid of the trace and layout files won’t make prefetching any better, it will just force them all to be recreated, thus slowing down the initial launch of all applications until this is reconstructed.\u00a0 Windows actually cleans out the folder itself whenever it needs it, so it’s best just to leave it alone.<\/p>\n Which brings me back around to Windows 2000, the venerable operating system on which my tablet runs Firefox.\u00a0 Win2k has no prefetching system, so that alternative strategies need to be employed.<\/p>\n This leads to an alternative strategy called “preloading,” which is not like prefetching at all, but more like loading Firefox and minimizing it, where much of Firefox is actually in memory.\u00a0 Early versions of Firefox included a “turbo launcher,” which was a little bit of software that loaded Firefox in memory so that it would be handy.\u00a0 This is no longer included, but a third party built a “Firefox Preloader,” which for all intents and purposes is the same thing.<\/p>\n The project is essentially dead, since prefetching made preloading less useful for XP and later versions of Windows.\u00a0 However, it does <\/em>work for the latest versions of Firefox, and it works quite well on Windows 2000.\u00a0 The installer can be downloaded here:<\/p>\n http:\/\/sourceforge.net\/projects\/ffpreloader\/<\/a><\/p>\n It works by looking for “Firefox.exe” and then loading it into memory.\u00a0 Next time firefox.exe is launched, nearly everything it needs is already in memory instead of loaded from disk.\u00a0 Prefetching makes this nearly pointless on XP, but the speed difference on an old Win2k box is stunning — assuming you actually have enough RAM to leave Firefox constantly in memory.<\/p>\n","protected":false},"excerpt":{"rendered":" If you’re like me, a considerable amount of your computing experience takes place within Firefox.\u00a0 I have a couple of old, slow computers, however, for which the actual loading speed of Firefox itself is problematic.\u00a0 Either can keep up fine with web content, and their connections are fast, but Firefox \u2026 Continue reading