I'm importing the water bodies theme using v.in.ogr. There are 89,173
nodes and 99,129 primitives and boundaries. The process cleans polygons,
breaks polygons, and removes duplicates very quickly. Then it seems to take
forever (more than 40 minutes in one attempt) while breaking boundaries.
This is on a moderately fast AMD-powered machine. Top shows two v.in.ogr
processes (one running 98 minutes, the other 12 minutes) consuming about 98%
of the CPU and about 23% of 2G RAM each process.
I'm importing the water bodies theme using v.in.ogr. There are 89,173
nodes and 99,129 primitives and boundaries. The process cleans polygons,
breaks polygons, and removes duplicates very quickly. Then it seems to take
forever (more than 40 minutes in one attempt) while breaking boundaries.
Update: I killed both processes and started anew. The v.in.ogr process to
break boundaries has been running for 10 minutes. Similar themes
(streams/rivers, hydrological units) completed much faster.
I'm importing the water bodies theme using v.in.ogr. There are 89,173
nodes and 99,129 primitives and boundaries. The process cleans polygons,
breaks polygons, and removes duplicates very quickly. Then it seems to take
forever (more than 40 minutes in one attempt) while breaking boundaries.
This is on a moderately fast AMD-powered machine. Top shows two v.in.ogr
processes (one running 98 minutes, the other 12 minutes) consuming about 98%
of the CPU and about 23% of 2G RAM each process.
In then best case the both, 6.5 for daily work, 7.x as experimental to
test new great features
Martin,
Thanks for the input. So 6.5 is sufficiently stable for production work
while 6.4 is still at RC5? Hmmm-m-m. That's interesting.
Perhaps this evening I'll build 6.5 and try it. Right now the CPU is
consumed with breaking boundaries on the standing water body theme for all
of Oregon ... I didn't realize there were so many lakes and reserviors!
Should I be running 6.5 or 7 rather than the 6.4.0svn from last week?
The changes to v.in.ogr as in ticket #426 apply only to grass7. v.in.ogr in grass65 should take as long as in grass64, not much difference there AFAICT.
The changes to v.in.ogr as in ticket #426 apply only to grass7. v.in.ogr
in grass65 should take as long as in grass64, not much difference there
AFAICT.
Markus,
OK. That's what I thought after looking at the ticket. That theme -- water
bodies -- took 3 hours to finish breaking boundaries. I guess that when I do
the soils today I can expect similar times.