Profiling about webgazer

[alexpapster]

Could we use transitions for more efficiently move the prediction location?

[Skylion007]

I've done some profiling with Google Chrome's profiler. Most of the bottlenecks where in clmtrakr as expected. One potential area of optimization is the LUDecomposition in the mat.js file as that was taking up a significant fraction of the execution time.

[Skylion007]

Here are the three prime spots for optimization that I have identified:

1. The ridge() method and it's submethod is probably our best bet for improved performance.
2. track() inside of CLMR tracker
3. getPupilFeatures() and it's methods in CLMGaze is also in need of potential optimization.

[jeffhuang]

Performance improved in a7962dc

At this point, we're at a local limit of what we think we can improve performance-wise. Please open a new issue with specific ideas for improving the performance.