However, the picture changes if ten sites are loaded at the same time. Safari is the most memory-frugal, while Firefox is the biggest memory-hog. With only one web site to display, the browsers use between 18.5MB and 35.3MB of memory under Mac OS X 10.5.2. We chose sites without advertising, since the constantly changing content of such sites does not allow for reproducible results: for example, one time you may get a simple image, while the next time the page is loaded a Flash animation may appear. A second test measures the resources needed to load 10 tabbed sites. In the first test, a web site is loaded and memory consumption measured. Although the CPU load is pretty consistent among the browsers, this is not the case with memory consumption. Opera and Safari also deliver significant performance improvements in their respective betas.Īs well as pure performance, it's important to consider the browsers' resource requirements. Among the beta versions, Firefox 3 Beta 5 is particularly impressive compared to its predecessor, reducing Firefox 2.0.13's 3.91 seconds to just 1.07 seconds in the HTML/JavaScript DOM test. These tests also demonstrate the benefits that browser development can deliver. Safari is the winner in the JavaScript tests too. Opera brings up the rear in this test, and this time the 9.5 beta brings no improvement. In the XML/CSS test, Safari again takes first place - and here, the STAND plug-in has no significant impact on performance. The beta version of Opera 9.5 manages to reduce the load time from over 48 seconds in version 9.27 to less than 20 seconds. However, the STAND Safari plug-in extends the load time to over 18 seconds - perhaps because it prevents the premature page-loading statement normally reported by iBench. Safari 3.1.0 is quickest in the HTML tests with a time of under 10 seconds, placing it well ahead of Opera 9.27's 48 seconds. Even so, despite these caveats, there's no doubt that Safari is indeed a fast browser. This is because, as mentioned earlier, iBench uses the JavaScript 'onload' event to determine page loading time, which Safari triggers before the page has in fact finished loading. However, these benchmark results should be treated with caution: manual measurements with a stopwatch show that Safari is not quite as fast as iBench suggests. Jobs' statement that the fastest Safari browser is based on tests the company has carried out using iBench 5.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |