[GRASS-dev] GRASS & cygwin quite slow

[Glynn Clements]

Moritz Lennert wrote:

> Now, several colleagues working in a MS Win environment would like to 
> try GRASS. However, after having installed the Cygwin+GRASS combination 
> (using the grass-cvs package from http://geni.ath.cx/grass.html) for 
> several colleagues, I have noticed that GRASS is quite slow, at least 
> diplaying vector maps. If I can't get this to speed up, it will be an 
> immediate showstopper for most of my colleagues.
> 
> I know I could tell them to use QGIS, but currently, the capacities of 
> QGIS in terms of vector mapping (which is what most of my colleagues do 
> - currently mostly with ArcView) are just too limited compared to GRASS.
> The other option is obviously to wait for the new GRASS python 
> interface. But as the dynamic is launched now, I would hate to tell 
> people: GRASS is great, just wait a bit.
> 
> So: is the cygwin solution slow because of the cygwin layer in between ? 
> Because of the X-server ? What might be a solution to speed things up ?

Are you displaying the maps with XDRIVER or with gis.m?

If you're using gis.m, the X server isn't involved in rendering the
maps; gis.m uses the PNG driver to render them into an image.

-- 
Glynn Clements <glynn at gclements.plus.com>