Run this simple test inside your browser of choice...

General Topics
1

Hi malware fighters,

http://openjsan.org/src/t/th/theory/Test.Simple-0.29/tests/index.html

polonus

2

All tests successful, 1 subtest skipped.
Files=18, Tests=294, 4.945 seconds

Is this good or bad?

3

Hi YoKenny,

It is nothing actually, it is just that your browser is working these javascript tests correctly.
If you had JS blocked, it would not run,
I wanted the speed of it to run in a specific browser,

flock is somewhat slower as your results were
All tests successful, 1 subtest skipped.
Files=18, Tests=294, 5.514 seconds

GoogleChrome gives:
All tests successful, 6 subtests skipped.
Files=18, Tests=294, 13.384 seconds
Not good for GoogleChrome…

SRWare;s Iron does it somewhat better in speed,
but skipped the same subtests:
All tests successful, 6 subtests skipped.
Files=18, Tests=294, 5.691 seconds

browzar IE browser shell is worst:
All tests successful, 1 subtest skipped.
Files=18, Tests=294, 33.078 seconds

Interesting as we get more results here from various browser users…

polonus

4

The previous was IE8 on Windows 7.

This is IE8 on XP Pro:
All tests successful, 1 subtest skipped.
Files=18, Tests=294, 15.219 seconds

5

Hi YoKenny,

So the end-result is also platform dependent, not only dependent on the javascript rendering of the browser.
Important what we do here, my friend, ergo conclusio the results are not equal to what everybody puts out as a sort of browser adagio, and we demonstrated that, thanks for your cooperation, I believe in what I can measure actually…

polonus

6

Here are some results on Windows 7 Ultimate 32 bit:

7

Hi bob3160,

Thanks for the results, GoogleChrome is specific here. Find out later why that is.
Well, you can generally ignore “skipped” notices, they just indicate that a required module is unavailable.
Where we have to look into it is where we get a “failed”…
The issue about browser memory is not “how much it takes now” but “how much it is going to take in an hour or two”. Besides the work done on Gecko and the JS engine to fix the memleaks, I guess they also have worked on the way memory is allocated and freed by the browser, with some sort of “garbage collection”. I give you a basic example, by default Firefox doesn’t free memory when they are minimized. But there is an option you can add as “true” in “about:config” (config.trim_on_minimize) that does exactly that etc. etc.

Damian

8

My results on vista 64bit machine. 1 using 64bit ie8.

9

Hi RNfromTN,

That is fast rendering, wow. Thanks for reporting here…

pol

10

IE8 on Windows 7 H/P

All tests successful, 1 subtest skipped.
Files=18, Tests=294, 4.128 seconds

11

Windows XP SP3, Firefox 3.5.4,
All tests successful, 1 subtest skipped.
Files=18, Tests=294, 9.08 seconds

And IE8
All tests successful, 1 subtest skipped.
Files=18, Tests=294, 3.797 seconds

12

[font=Segoe UI]Google Chrome 4.0.222.12
[font=Segoe UI]
[]All tests successful, 6 subtests skipped.
[]Files=18, Tests=294, 18.491 seconds

13

My results, using FF 3.5, and 3.6 (both the portable versions, if it matters)

Interesting to see that the newer one is quicker, although I don’t know how the ‘out of the box’ settings of 3.6 affect this test…

-Scott-

14

Windows XP SP3 Firefox 3.5.4

All tests successful, 1 subtest skipped.
Files=18, Tests=294, 5.842 seconds

15

Due to the different environments, if you are going to post the test results at all, it would be more fruitful if you post the results of different browsers under the same environments as polonus and some others did.

I thought the speed of SRWare Iron nealy equals to that of Chrome. Consideing the last update of SRWare Iron being 09.08.09, there may be no wonder in this, though. Also, SRWare Iron and Chrome skip 6 sub-tests, which means, they are “cheating”? It’s interesting since Firefox is yet to pass Acid 3 test.

This depends on how we use the browser, too, I think. I tend to keep FF once it’s open while I close SRWare Iron whenever I finished browsing.

3.6 should be quicker since better java-handling is one of the features to be improved.

Feel the speed with improved JavaScript performance, browser responsiveness, and startup time.
16

here’s mine with FF 3.5.4

17

:-\ Er…

18

Oh sorry, I took the subject line literally.
“Run this simple test inside your browser of choice…”

(I don’t use any other browsers)

19

I see… Then, the blame goes to polonus… ;D Well, thinking of it, sometimes, I also do posts after reading the original post without reading all the other posts. So, no problem. :wink:

20

These are results on my XP SP3 desktop.
Firefox 3.5.4
IE 8.
RoRo