[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                    |  
--------------------------------------+-------------------------------------
Changes (by justinzane):

  * cpu:  Unspecified => x86-64


Comment:

 Thanks for the response. I cannot post the dot graphs because of size
 restrictions, and resizing them makes them near unreadable.

 I did another little experiement, and, it seems that the problem is
 **not** with the database driver at all. WRT MySQL and SQLite, it is the
 location of the 'grassdata' folder that is at issue. I had kept
 'grassdata' on an NFS mount. Moving it to a local (btrfs) spinning disk
 meant that the import was **many** times faster (although moron forgot to
 add 'time' before the command :( ).

 I'm rebuilding an unstripped glibc and other dependencies to see exactly
 which calls may be problematic.

 As far as monitoring the mysql and v.in.ogr processes, do you have any
 recommended way besides running grass like:

 {{{
 perf record -e cycles:u -o grass.prof -g -- grass64 -text
 /home/justin/maps/grassdata/osm_data/OSM;
 ####
 # In grass shell [zsh]:
 # v.in.ogr dsn=./path/to/shape.shp output=shape
 # exit
 ####
 perf script -i grass.prof | gprof2dot -f perf  | dot -Tpng -o output.png;
 gwenview output.png
 }}}

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