GBIC >> Programming Languages - Performance
Programming Languages - Performance

Note: 22 July 2008 - I've just started on this page, so please watch for updates in the near future.

Speed of execution is a common definition of performance, as measure across a range of functions. I'm working to define a dozen or so algorithms to use in this analysis.

If I knew of a way to judge the time to create an application, I'd look at that as well. For example, the impact of integral tools or third-party tools impacts development time. But how long it takes to code a function is so dependent on the programmer that I'm not sure quite how to take out the variable human element. I'll think on it.

Algorithms
I've decided to test five different algorithms, as shown in the following table.

    Numeric Strings Graphics Combination File/Directory Access
    ... in work
    .
    .
    .
    .
    .
    .
    ... in work
    .
    .
    .
    .
    .
    .
    ... in work
    .
    .
    .
    .
    .
    .
    ... in work
    .
    .
    .
    .
    .
    .
    ... in work
    .
    .
    .
    .
    .
    .

Results
And here are the results of testing the algorithms. Additional explainatory comments are provided below the following table.

    Language Numeric Strings Graphics Combination File/Directory Access
    VB6 .. in work .. in work .. in work .. in work .. in work
    Perl .. in work .. in work .. in work .. in work .. in work
    PowerBASIC .. in work .. in work .. in work .. in work .. in work
    C# .. in work .. in work .. in work .. in work .. in work
    VB.NET .. in work .. in work .. in work .. in work .. in work
    Java .. in work .. in work .. in work .. in work .. in work
    LUA .. in work .. in work .. in work .. in work .. in work

Explanatory Comments
.. in work