wren/test/benchmark/map_numeric.wren

var start = System.clock

var map = {}

for (i in 1..2000000) {
  map[i] = i
}

var sum = 0
for (i in 1..2000000) {
  sum = sum + map[i]
}
System.print(sum)

for (i in 1..2000000) {
  map.remove(i)
}

System.print("elapsed: %(System.clock - start)")
"IO" -> "System". Get rid of the separate opt-in IO class and replace it with a core System class. - Remove wren_io.c, wren_io.h, and io.wren. - Remove the flags that disable it. - Remove the overloads for print() with different arity. (It was an experiment, but I don't think it's that useful.) - Remove IO.read(). That will reappear using libuv in the CLI at some point. - Remove IO.time. Doesn't seem to have been used. - Update all of the tests, docs, etc. I'm sorry for all the breakage this causes, but I think "System" is a better name for this class (it makes it natural to add things like "System.gc()") and frees up "IO" for referring to the CLI's IO module. 2015-09-15 07:46:09 -07:00			`var start = System.clock`
Adding map benchmark scripts. 2015-02-09 11:51:09 +01:00
			`var map = {}`

Fix horrendously bad bit hashing function. hashBits() is used to generate a hash code from the same 64 bits used to represent a Wren number as a double. When building a map containing a large number of integer keys, it's important for this to do a good job scattering the bits across the 32-bit key space. Alas, it does not. Worse, the benchmark to test this happens to stop just before the performance falls off a cliff, so this was easy to overlook. This replaces it with the hash function V8 uses, which has much better performance across the numeric range. 2019-07-27 13:34:07 -07:00			`for (i in 1..2000000) {`
Adding map benchmark scripts. 2015-02-09 11:51:09 +01:00			`map[i] = i`
			`}`

			`var sum = 0`
Fix horrendously bad bit hashing function. hashBits() is used to generate a hash code from the same 64 bits used to represent a Wren number as a double. When building a map containing a large number of integer keys, it's important for this to do a good job scattering the bits across the 32-bit key space. Alas, it does not. Worse, the benchmark to test this happens to stop just before the performance falls off a cliff, so this was easy to overlook. This replaces it with the hash function V8 uses, which has much better performance across the numeric range. 2019-07-27 13:34:07 -07:00			`for (i in 1..2000000) {`
Adding map benchmark scripts. 2015-02-09 11:51:09 +01:00			`sum = sum + map[i]`
			`}`
"IO" -> "System". Get rid of the separate opt-in IO class and replace it with a core System class. - Remove wren_io.c, wren_io.h, and io.wren. - Remove the flags that disable it. - Remove the overloads for print() with different arity. (It was an experiment, but I don't think it's that useful.) - Remove IO.read(). That will reappear using libuv in the CLI at some point. - Remove IO.time. Doesn't seem to have been used. - Update all of the tests, docs, etc. I'm sorry for all the breakage this causes, but I think "System" is a better name for this class (it makes it natural to add things like "System.gc()") and frees up "IO" for referring to the CLI's IO module. 2015-09-15 07:46:09 -07:00			`System.print(sum)`
Adding map benchmark scripts. 2015-02-09 11:51:09 +01:00
Fix horrendously bad bit hashing function. hashBits() is used to generate a hash code from the same 64 bits used to represent a Wren number as a double. When building a map containing a large number of integer keys, it's important for this to do a good job scattering the bits across the 32-bit key space. Alas, it does not. Worse, the benchmark to test this happens to stop just before the performance falls off a cliff, so this was easy to overlook. This replaces it with the hash function V8 uses, which has much better performance across the numeric range. 2019-07-27 13:34:07 -07:00			`for (i in 1..2000000) {`
Adding map benchmark scripts. 2015-02-09 11:51:09 +01:00			`map.remove(i)`
			`}`

Simple string interpolation. This allows "%(...)" inside a string literal to interpolate the stringified result of an expression. It doesn't support custom interpolators or format strings, but we can consider extending that later. 2015-11-11 07:55:48 -08:00			`System.print("elapsed: %(System.clock - start)")`