Re:In Erlang/OTP 27, +0.0 will no longer be exactly equal to...
by FpUser on Tuesday May 09, 2023 @04:45PM
(#35880149)
I would add generating large financial reports, enterprise billing etc. There is a huge business effect between for example 2 hours needed to calculate monthly invoices and 24 hours.
[ Parent
| on HN ]
Re:In Erlang/OTP 27, +0.0 will no longer be exactly equal to...
by wtallis on Tuesday May 09, 2023 @04:47PM
(#35880172)
Is any of that actually bottlenecked by arithmetic rather than pointer chasing?
Re:In Erlang/OTP 27, +0.0 will no longer be exactly equal to...
by syastrov on Tuesday May 09, 2023 @07:14PM
(#35881588)
Probably more likely inefficient data access patterns, such as N+1 queries, inefficient algorithms, lack of parallelism
Re:In Erlang/OTP 27, +0.0 will no longer be exactly equal to...
by kragen on Wednesday May 10, 2023 @01:39PM
(#35890677)
no, 2 hours of addition on my cellphone at 2 gigahertz, 4 cores, and conservatively 3 additions per core per cycle would be 170 trillion additions
nobody needs 170 trillion additions for their nightly invoices