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

 Replying to [comment:6 justinzane]:
 > I'm greatly interested in guidance on narrowing down the bottleneck with
 "grassdata" on a NFS mount, but I may need some assistance in the process.

 I don't know much about perf, but I do have some experience with accessing
 a GRASS database over NFS (multiple clients accessing the same GRASS
 database over NFS at the same time). The problem seems to be not the GRASS
 + NFS combination, but the connection to the NFS server (should be at
 least a Gigabit connection and static IP addresses for the server and all
 its clients) and other traffic simultaneously going to the NFS server from
 other clients.

 You could
  * check the IO traffic on the NFS server without using GRASS
  * copy some stuff, e.g. an unpacked Linux kernel, from the local disk
 over to the NFS mount and check the performance
  * investigate the actually used NFS mount options in /proc/mounts
  * try to tune NFS mount options, particularly rsize,wsize, bigger seems
 to be better, more in `man nfs`

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