[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 mmetz):

 Replying to [comment:47 neteler]:
 > Replying to [comment:46 mmetz]:
 > > Why have this also in relbr70? Backporting new features from trunk to
 a release branch is a bad idea and against GRASS policy,
 >
 > I wrote only that there must be one method to *read* compressed NULL
 files in G70. Not much of a big backport if I recall a personal discussion
 we had on this topic last year. That's all I meant above.

 Even only read support in G70 will require quite some changes to the
 rasterlib.
 >
 > Or we need to release trunk as G8 in order to be allowed to break raster
 readability compatibility completely.

 In your opinion:
 * Adding new compression methods in G71 for cell/fcell files that are not
 readable by G70 is ok.
 * Compression of null files in G71 not readable by G70 is not ok.

 That does not make sense to me. Please explain.

 BTW, the new compression methods for cell/fcell files available in trunk
 have a much larger impact on performance and disk space requirements than
 null file compression.

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