[GRASS-dev] [GRASS GIS] #2185: Painfully Slow 'v.in.ogr' Vector Import
GRASS GIS
trac at osgeo.org
Tue Feb 4 14:11:48 PST 2014
#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 justinzane):
[quote]check the IO traffic on the NFS server without using GRASS[/quote]
Did, using iotop while running v.in.ogr -- No noticeable IO besides my
GRASS import, which is expected since it is a personal server.
[quote]copy some stuff, e.g. an unpacked Linux kernel, from the local disk
over to the NFS mount and check the performance[/quote]
Works swimmingly for large files. I updated the post at
[www.justinzane.com/grass-perf.html] to show a simplistic test. Basically,
though my Dell laptop has a castrated NIC -- the 4 gigabit pins are not
connected! -- NFS works at almost line speed. Throughput is not the
problem, rather it seems to be excessive opens/syncs/similar that is the
issue.
Using `nfsstat -Z10`, I get about 27 writes per second. Which seems to
equate to one write per primitive! I'm a GIS novice, but it seems that
writing for every primitive is not efficient from a programming
perspective. Am I missing something?
[quote]investigate the actually used NFS mount options in
/proc/mounts[/quote]
{{{nfs4
rw,relatime,vers=4.0,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.182,local_lock=none,addr=192.168.0.10
0 0}}}
[quote]try to tune NFS mount options, particularly rsize,wsize, bigger
seems to be better, more in man nfs [/quote]
With writes of a few bytes to a few kB, this does not matter.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2185#comment:8>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list