Help!: [Sticky] How to Deal with Slow Mapping Tool - Tips for Performance

Some users have complained that the site is slow, even on fast internet connections. Here are some tips to help:

1. Use Firefox - We test the site across a variety of browsers, and in almost all cases, Firefox is the clear performance winner. If you're not familiar with Firefox, it is a free browser, available on most platforms from http://www.getfirefox.com. The performance differences can be shocking, especially compares to Internet Explorer 6.0. If you're on windows and insist on using Internet Explorer, it will work, but please use at least version 7 for good performance. For the mac users, Safari's in the same boat...it should be functional on the site, but it isn't as fast as Firefox.
2. Check your memory - Our sites are accessed via the Internet, but the routing application still needs to use the horsepower of your computer to do most of it's work. The biggest variable here is RAM, and as always, the more the better. For most uses, we recommend systems with at least 1GB of RAM, however power users may want 2GB of RAM or more
3. Restart your browser - We have noticed that most web browsers tend to leak memory from time to time. This can cause your browser and computer to get in a state where it becomes very, very slow for what seems to be no reason. Sometimes the best solution is to simply restart your browser. Advanced users can check their browser process to see how much memory their using (i.e. via the task manager in Windows). I will often see firefox.exe processes using 250MB or memory or more, at which point it's time for a restart.
4. Check you routes- The more points your route has, the more 'juice' it requires from the route engine. If plotting long routes, try not to add points too densely. For GPS users uploading data, try to use a mode that reduces the number of points in your route data. For example, for Garmin Forerunner and Edge users, we highly recommend using "Smart Recording" mode for this purpose.

markgreenwood,

The iMac, like most other computers need to maintain a constant movement of bits and bytes over its gills; while it may seem beneficial to have ram up to the gills in reality this impedes the movement of bytes, bits are small enough to pass through unhindered, resulting in byteoxia; this condition can be fatal to younger, or otherwise immunodeficient individuals.

Okay, in all seriousness your condition sounds very unusual, can you please submit a bug report (that way we can get all your browser information) and try to replicate the issue.