You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@datasketches.apache.org by "Lee Rhodes (Jira)" <ji...@apache.org> on 2022/04/19 01:42:00 UTC

[jira] [Closed] (DATASKETCHES-10) Double precision by default?

     [ https://issues.apache.org/jira/browse/DATASKETCHES-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lee Rhodes closed DATASKETCHES-10.
----------------------------------
      Assignee: Lee Rhodes
    Resolution: Fixed

Will be fixed with datasketches-java 3.2.0

> Double precision by default?
> ----------------------------
>
>                 Key: DATASKETCHES-10
>                 URL: https://issues.apache.org/jira/browse/DATASKETCHES-10
>             Project: Apache Datasketches
>          Issue Type: Improvement
>            Reporter: Jan Prach
>            Assignee: Lee Rhodes
>            Priority: Major
>
> Would it make sense to use double (instead of float) for all sketches by default?
> It would take (less than 2x) more memory, have same speed, have twice the storage. Or even the same storage if one is fine with the flaot precision. Most importantly it would be far more useful.
> I' trying to build generic profiler. In the first simple dataset there were a couple of date  and timestamp columns. The obvious choice is to convert them to epoch seconds. Full day of time with weird messages only to realize that KllFloatsSketch, ReqSketch, etc. are all based on floats. That means 24 bit precision. But epoch seconds today are 31 bit numbers.
> Why not always double?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
For additional commands, e-mail: dev-help@datasketches.apache.org