[GRASS-dev] [GRASS GIS] #2750: LZ4 when writing raster rows; better than double I/O bound r.mapcalc speed

[GRASS GIS]

#2750: LZ4 when writing raster rows; better than double I/O bound r.mapcalc speed
--------------------------+---------------------------
  Reporter:  sprice       |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.1.0
 Component:  Raster       |    Version:  svn-trunk
Resolution:               |   Keywords:  ZLIB LZ4 ZSTD
       CPU:  OSX/Intel    |   Platform:  MacOSX
--------------------------+---------------------------

Comment (by wenzeslaus):

 I have
 [https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html
 #running-tests-report executed all tests] with `lz4_zstd2.tgz​` and I got
 22 (17%) more failing tests, unfortunately. One example is `r.viewshed`
 test where the results are just completely wrong:

 {{{
 ...
 mismatch values (key, reference, actual):
 [('max', 43.15356, -3.44000005722046),
  ('min', -24.98421, -3.44000005722046),
  ('null_cells', 1963758, 0)]
 ...
 }}}

 I haven't investigated further. Can anybody confirm or disproof?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2750#comment:2>
GRASS GIS <https://grass.osgeo.org>