Skip to main content

Sieve benchmarks

After comparing the performance of Run Basic (Beta) and Liberty Basic 4.03 using the Sieve sample program, I wanted to expand the comparison to include a few other languages. I ported the Sieve program as directly as possible. Here are the test results sorted from low to high:

Find primes from 0 to 7000 (10-run average in milliseconds)
  • Visual Basic 6.0 (0.0)
  • Run Basic (28.8)
  • REBOL (35.9)
  • Runtime Revolution (63.7)
  • Liberty Basic 3.03 (146.8)
  • Liberty Basic 4.04 (170.3)
Find primes from 0 to 1000000 (10-run average in milliseconds)
  • Visual Basic 6.0 (273.5)
  • Run Basic (4164.4)
  • REBOL (4767.2)
  • Runtime Revolution (12421.5)
  • Liberty Basic 3.03 (20381.1)
  • Liberty Basic 4.04 (27732.9)
I ran the 0-1000000 benchmark to get VB off of zero milliseconds for a better comparison.

Comments

Popular posts from this blog

Run BASIC Hosting Service Launched

The new Run BASIC hosting service launched at midnight! Please visit http://runbasichosting.com for more details. Monthly and annual subscriptions are available. Run BASIC , a product by ShopTalk Systems, is a tool that makes it easy to create your own web applications. No computer science degree required . Run BASIC Hosting is a service that makes it easy to deploy your applications to the Internet. No IT experience required .

How to set the System Restore and Shadow Copy storage limit in Windows Vista

I ran into a problem recently where Windows Vista kept using up all of my available disk space for System Restore and Shadow Copy storage. There is a feature in the Disk Cleanup utility that lets you manually delete all but the most recent snapshot. I did that for months before I finally took the time to figure out how to set the limit. My problem was pretty extreme. My HP Pavilion laptop has a 105 gig disk drive. I have about 47 gigs free and over a period of about a month, Vista would use it all up. Vista is supposed to use only 15% of the hard disk for this storage, but apparently sometimes that limit can become UNBOUNDED. I don't know how that happens. To see the current setpoint for your system, go to a command prompt and type the following: vssadmin list shadowstorage You should see something like the following: To change the current setpoint for your system, type the following but change what's necessary to match your system. For example, you may need to change the drive