Link Details

Link 179052 thumbnail
User 207602 avatar

By jimbojw
Submitted: May 01 2009 / 12:39

Many readers pointed out (correctly) that my exposition on efficient JavaScript string building was in need of benchmarking numbers to be of real value. This article provides those number for several browsers, along with a simple test suite you can try yourself.
  • 3
  • 0
  • 525
  • 0
User 368023 avatar

yakkoh replied ago:

0 votes Vote down Vote up Reply

Let's be fair: the test "Internet Explorer 6 (via wine) is ... " does not count.

User 207602 avatar

Jim Wilson replied ago:

0 votes Vote down Vote up Reply

Hi yakkoh,

Thanks for taking the time to comment. It depends on what you mean. If the purpose of the benchmark was to compare /browser implementations/ then yes, I completely agree that running any browser on a non-native platform is an unfair test.

However, the purpose of the benchmarks is to compare JavaScript function implementations against each other. From that standpoint, I feel that comparing how one JavaScript function runs in IE 6/wine vs another is at least somewhat relevant, since the same OS process is responsible for the results of both tests. That is, any performance implications of running in wine ought to affect all implementations, right?

Ok, well, maybe not. Maybe wine puts a higher penalty on memory allocation than native Windows, which would unduly penalize the string buffer implementation more than others. That might be worth investigating in its own right.

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Upvoters (3)

Downvoters (0)

    Apache Hadoop
    Written by: Piotr Krewski
    Featured Refcardz: Top Refcardz:
    1. Play
    2. Akka
    3. Design Patterns
    4. OO JS
    5. Cont. Delivery
    1. Play
    2. Java Performance
    3. Akka
    4. REST
    5. Java