[GRASS-dev] [GRASS GIS] #2185: Painfully Slow 'v.in.ogr' Vector Import

[GRASS GIS]

#2185: Painfully Slow 'v.in.ogr' Vector Import
--------------------------------------+-------------------------------------
 Reporter:  justinzane                |       Owner:  grass-dev@…              
     Type:  defect                    |      Status:  new                      
 Priority:  normal                    |   Milestone:  7.0.0                    
Component:  Vector                    |     Version:  svn-trunk                
 Keywords:  import, OGR, performance  |    Platform:  Linux                    
      Cpu:  x86-64                    |  
--------------------------------------+-------------------------------------

Comment(by mmetz):

 I did some tests with and without NFS, importing a shapefile with 50000
 points and 19 attribute fields:
  * shapefile on local disk, grassdata on local disk: 12000 points / sec
  * shapefile on local disk, grassdata on NFS: 2200 points / sec
  * shapefile on NFS, grassdata on NFS: 2100 points / sec
  * shapefile on NFS, grassdata on local disk: 11000 points / sec

 Here, writing to grassdata on NFS is also much slower, but always much
 faster than about 20 points / sec. The NFS server here is not at all a
 high-performance server, instead designed for power-saving.

 Your minifstest gives here

 {{{
 NumChars: Local (s)   NFS (s)  NFS/Local
 00000002:  000.0100, 000.0200, 002.0000
 00000004:  000.0100, 000.0200, 002.0000
 00000008:  000.0200, 000.0300, 001.5000
 00000016:  000.0200, 000.0400, 002.0000
 00000032:  000.0400, 000.0400, 001.0000
 00000128:  000.1300, 000.1600, 001.2308
 00000512:  000.5200, 000.5300, 001.0192
 }}}

 The penalty for doing lots of tiny open-write-close cycles on NFS is here
 maximum 2, not 7.

 IMHO, something is strange with your NFS server, but I have no idea what.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2185#comment:9>
GRASS GIS <http://grass.osgeo.org>