[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, v.in.ogr  |    Platform:  Linux                    
      Cpu:  x86-64                              |  
------------------------------------------------+---------------------------
Changes (by hamish):

  * keywords:  import, OGR, performance => import, OGR, performance,
               v.in.ogr


Comment:

 @justinzane: if you get a few moments could you add a quick example on our
 wiki of how end users can run `pref`? tx.
  http://grasswiki.osgeo.org/wiki/Bugs#Using_a_profiling_tool

 @mmetz: some sample OSM data to test is available here:
  http://download.osgeo.org/livedvd/data/osm/


 I'm still not understanding if this trouble is CPU bound, local IO bound,
 or network bound. Some combo of top, iotop, iftop, and gkrellm would
 hopefully shed some light on that without having to push everything
 through a profiling tool. What does 'top -i' show about the v.in.ogr and
 sqlite processes and kernel %use state?
 is it dead locked? spending all its time in the kernel? libogr..?


 regards,
 Hamish

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