New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiling #129

merged 3 commits into from Dec 28, 2017


1 participant

matatk commented Dec 28, 2017

Add a basic test script to create some profile data.

Note the unexpected lack of traces to shouldRefreshLandmarks() discussed in commit 2c6fba1.

matatk added some commits Nov 22, 2017

Initial profiling support
Have tried many different numbers of repetitions, wait times and steps
paramater for the mouse move, but only ever showing one or two (very
rarely four) calls to shouldRefreshLandmarks() and not really sure why.

Actually, on further testing, it seems that the number of calls to
shouldRefreshLandmarks() varies across runs of the trace. Nowhere near
as many calls as actually happen are picked up (assuming this is down to
timing resolution), but the number picked up does vary across runs.

Still, the main purpose of this is to streamline the functions that take
the longest, i.e. the landmarks-finding code. Would like to grok this
whole tracing thing, though...

@matatk matatk merged commit 3f01cf4 into master Dec 28, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
continuous-integration/travis-ci/push The Travis CI build passed

@matatk matatk deleted the profiling branch Dec 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment