[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
At 9:15 AM -0800 2/14/11, Gregg Tavares (wrk) wrote:
So I probably shouldn't respond to this because being on the Chrome team no matter what I say it will sound defensive but:
I'm very glad you did respond ... I'm pretty new to this and I shared this just to open this kind of discussion.
*) Are you sure these are valid tests?
I don't know much about benchmarking the matrix operations. This code is based on Brandopn's work.
The input matrices to the tests are created with random values so that presumably makes optimization less of an issue.
*) Are you sure they are computing the same things? For example mjs doesn't appear to have a true matrix inverse so you're comparing apples to oranges vs the other libraries there.
*) I added the math library from the tdl stuff. They are slightly faster at some things and slower at others. Attached (sorry, new to git)
Thanks, I've pushed your tdl library addition to the git repo so they're now included also.
The graph now updates in real-time also.
*) Matrix math isn't everything. For example running the webgl aquarium on FF4b11 vs Chromium 11.0.668.0 (74525) on your hardware (I have the same machine) using this url
At 50 fish
At 1000 fish
Yes, definitely true.
I did this work because I wanted to pick a matrix library to use (and I needed to learn more about flotr for a related project).
I was surprised that the only library that seems to have a relatively large number of unit tests is Sylvester.
- tdl is fast and has nice documentation in the code but no tests
- glmatrix is fast and has four tests
- mjs is fast, has html documentation in the repo.
- ewgl is slower and doesn't seem to have much doc in the repo
Of course none of that explains why FF is 5 times faster for your test as it is.
Yes ... I find that a mystery also.
I am curious if other people using different computers also see a similar speedup in Minefield and a similar slowdown in WebKitnightly?