v.support VERY slow

[Chris C Rewerts]

Eric:

Don't be suprised if it takes 5 days, not hours...
I have some experience in importing dlg files to grass vect
on a well-outfitted sparc 2. Seems to me it took v.support
close to 5 days to do topology on a road map of the St. Louis area.
However, this was a machine I share with others, so I run
a script to do the importing and I use "nice +15" so that 
I don't bog the machine down when other things are happening.
As long as the disk space holds and no one reboots the machine,
et cetera, it is no big deal. I have the script capture stdout
and stderr to a file for reference and then it sends mail when
maps are done.

>From lists-owner at amber.cecer.army.mil Wed Aug  5 20:14:29 1992
>From: kostello at muir.sscnet.ucla.edu (Eric Kostello)
>Subject: v.support VERY slow
>
>The subject is really:
>v.support is very slow even on a Sparc 2 on files derived
>from Los Angeles County TIGER Files....
>
>I imported the Los Angeles County TIGER file with v.in.tiger
>then ran v.support. The tutorial for "TIGER in GRASS" warns that
>this may take up to several hours, but it has taken nearly 48
>hours and it's still not done.
>
>System Configuration:
>Sparc 2, 48MB RAM, Plenty of disk space.
>Running under OpenWindows
>
>It wrote the file la.Master after about 30 hours in the dig_att
>directory.
>
>What I really want to know is whether this is normal for huge 
>(e.g. 65MB for type 1) TIGER files or if something has gone 
>awry. I'm a new GRASS user and we just got GRASS running here
>so there may be some problems with our configuration.....
>Any advice on this will be greatly appreciated.
>
>
>Thanks.
>Eric Kostello
>kostello at muir.sscnet.ucla.edu
>