Nine languages benchmarked
The following is a "Nine Language Performance Round-up, Benchmarking Math & File I/O". Accurate? Dunno. Interesting, though.
| int math | long math | double math | trig | I/O | TOTAL | |
| Visual C++ | 9.6 | 18.8 | 6.4 | 3.5 | 10.5 | 48.8 |
| Visual C# | 9.7 | 23.9 | 17.7 | 4.1 | 9.9 | 65.3 |
| gcc C | 9.8 | 28.8 | 9.5 | 14.9 | 10.0 | 73.0 |
| Visual Basic | 9.8 | 23.7 | 17.7 | 4.1 | 30.7 | 85.9 |
| Visual J# | 9.6 | 23.9 | 17.5 | 4.2 | 35.1 | 90.4 |
| Java 1.3.1 | 14.5 | 29.6 | 19.0 | 22.1 | 12.3 | 97.6 |
| Java 1.4.2 | 9.3 | 20.2 | 6.5 | 57.1 | 10.1 | 103.1 |
| Python/Psyco | 29.7 | 615.4 | 100.4 | 13.1 | 10.5 | 769.1 |
| Python | 322.4 | 891.9 | 405.7 | 47.1 | 11.9 | 1679.0 |
Benchmarking 9 languages
The Ghetto Mini-Pattern
No, this doesn't involve tales of Warsaw or Rick James. As a designer, architect or developer, have you ever been confronted with an unwieldy, nasty, fugly ball of application code that desperately needs a rewrite? Yet, there's too much working business logic to simply throw it away. Enter the Ghetto mini-pattern.
...Hide your ugly code inside a Ghetto. The ghetto is a single file or class where issues of code cleanliness do not apply. It is entered by reputable developers with no small amount of trepidation, and left as quickly as possible. On the other hand, it does the job, and it keeps the bad elements away from more cultured code...
Name: The Ghetto
DARPA and P2P
"S" emailed me a hookup to this article in which DARPA is funding several efforts to improve P2P architectures for the raw processing power, bandwidth efficiencies, fault-tolerance in routing, and so forth.
Darpa is pushing toward a world of ultralow-cost, low-power, ad hoc mesh networks. The programs are part of a broad military drive toward ubiquitous computing based on next-generation networks, including RFID and wireless sensor nets...
DARPA looks past Ethernet, IP nets
No comments:
Post a Comment