Skip to content
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.

Allow floating point times #10

Merged
merged 3 commits into from
Jul 30, 2014
Merged

Allow floating point times #10

merged 3 commits into from
Jul 30, 2014

Conversation

zerowidth
Copy link
Member

The experiments we've been doing have been using the #timing method to ship floating point millisecond values, and when we switched our code over to using the #time { ... } blocks, I noticed our measurements were locked to integer millsecond values and often being rounded down to 0 for sub-millisecond times.

This PR changes the client to allow us to track sub-millisecond performance timing. The spec says "integers", but everything else disagrees, transmitting and storing everything as doubles:

cc @vmg @jssjr @azizshamim

If y'all approve, I'll package this gem and roll it into a PR internally.

To match what the available back-ends support.
To prevent potential problems with repeating decimals, e.g. 0.3333333333333.
zerowidth added a commit that referenced this pull request Jul 30, 2014
@zerowidth zerowidth merged commit 4be5ca3 into master Jul 30, 2014
@zerowidth zerowidth deleted the allow-floating-point-times branch July 30, 2014 15:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
1 participant