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

GRASS GIS trac at osgeo.org
Mon Oct 12 04:02:53 PDT 2015


#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 glynn):

 Replying to [comment:13 wenzeslaus]:

 > My question is if it wouldn't be more advantageous to create some
 wrapper which would take the all necessary inputs including compression
 type and do the necessary switches and format specific things.

 Agreed.

 In practical terms, there are only two distinct cases: uncompressed (where
 the size of the data read or written matches the size of the data stored
 in the file) and compressed (where the sizes differ). Everything else is
 just options.

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



More information about the grass-dev mailing list