[GRASS-dev] r.surf.contour inefficiency?

[Markus Neteler]

On Sun, Feb 8, 2009 at 8:26 AM, Glynn Clements <glynn at gclements.plus.com> wrote:
> I'll remove the segmentation code in 7.0.

Here the timing comparison:

# NC data set
g.region vect=elev_lid792_cont1m res=1 -p
v.to.rast elev_lid792_cont1m out=elev_lid792_cont1m use=z
time r.surf.contour elev_lid792_cont1m out=dem

Results:
* GRASS 6.5.svn (pre seg size update):
147.66user
24.14system
2:52.22elapsed
184inputs+4544outputs (1major+508minor) pagefaults 0swaps

* GRASS 6.5.svn (post seg size update):
118.28user
0.26system
1:58.93elapsed
0inputs+4984outputs (0major+1202minor)pagefaults 0swaps

* GRASS 7.svn:
72.19user
0.04system
1:12.38elapsed
0inputs+320outputs (0major+1023minor) pagefaults 0swaps

r.univar doesn't show differences between 6.5.svn (post seg size update)
and 7.svn.
Is there risk in backporting this?

Markus