“The benchmark numbers are completely wrong for both databases”
1–10 of 58 posts
Re: “The benchmark numbers are completely wrong for both databases”
#2Re: “The benchmark numbers are completely wrong for both databases”
#3...forgot to call run().
Still we don't know the hardware, what versions were installed, configuration changes etc.
The whole thing is pretty meaningless.
Re: “The benchmark numbers are completely wrong for both databases”
#4Benchmarking programming languages got better. E.g.: http://benchmarksgame.alioth.debian.org/ gives roughly idea about performance of programing languages.
I wish something similar existed for databases. I think exact figures would be hard to get, but I believe there are many 2x 10x differences that we should be aware of.
Re: “The benchmark numbers are completely wrong for both databases”
#5He does have a point there. It is slightly annoying having to type out a query when I just want to browse the data. (No real biggie though..)
Re: “The benchmark numbers are completely wrong for both databases”
#6Re: “The benchmark numbers are completely wrong for both databases”
#7benchmark = marketing (more times than not)
Re: “The benchmark numbers are completely wrong for both databases”
#8Re: “The benchmark numbers are completely wrong for both databases”
#9Re: “The benchmark numbers are completely wrong for both databases”
#10benchmark = marketing (more times than not)
And it's an important (albeit just one part) of deciding which product to use.