opened
bernardd
username_0
The `reverse_byte_order/1` function was not especially quick. In an Ecto postgres query with a large number of geo fields, it ended up taking a significant percentage of the total time. I have some `fprof` files if you're interested in details, but the short version is that this change reduced the time to process the geo fields on 2000 objects (running under `fprof`, so the times are larger than they would otherwise be) from 1358ms to 142ms for the same query (the first value represented 42% of the total query time).
Optimise reverse_byte_order/1
issue
created
bryanjos
username_1
Awesome! thanks!
comment