from arcview 3.0 to arcgis 10.2, and from 2003 using Qgis.I think I followed everything correctly to get you the requested logs and am in great hopes you can help me.Ī little background, as requested. but the "layer size" issue is very common there too.
#COMPUTER ZEER TRAAG WINDOWS#
Qgis tend to run better under windows environment. take the shapes to my very old notebook and have the work done in a simple an fast way. So usually first I try to do it with QGis.and then, if not worked. Or cliping that dont perform on any "very complex" feature of the base layer.so the result its a clip layer that never perfomed the clip on a polygon so the clip have missed 30% of the area. compared to dissolve the very same layer on arcgis on an 10 years old notebook(core duo)+2Gb ram+ windows XP.that make it correctly on 10 minutes. a 6hs dissolve process on a 1330000 features layer (entire country.like half of united states) on Qgis on a new intel i5+8Gb ram + Ubuntu.that maybe also can crash in anytime. or in some cases take like 36 times to accomplish a pared to the same task (same shapes/layers perform the same process) in ArcGis. "cliping" or "dissolve" for me usually Qgis dont do it or just crashes. for some process the meaning of "big" may vary from 10mb to 250mb.ī) the layer have large multipart features (features made of "too many" parts)Ĭ) the layer have some (non multipart) features with "a lot of vertex/nodes" Qgis simply works "ok", unless you have any of this situations:Ī) the layer is big. I mention this here for the benefit of other new users.
I feel like a bit of an idiot for not having noticed it before, but turning off rendering greatly increases the speed with which I can accomplish tasks for which immediate re-rendering isn't critical. I just discovered the "Render" button at the bottom left of the QGIS map viewer. That figure is clearly discrepant with the size of the data set I described in my original post and it makes the slowness more understandable. This is frustrating because any modification of the project, however slight, requires a lengthy wait before the results can be assessed, and sometimes the application simply crashes without completing whatever I asked. No other memory-hungry applications are running concurrently. In fact, any change takes nearly that long, including renaming the single layer that really surprised me. Performance: Rendering takes 5-10 minutes. System: MacBook OS X 10.7.3, 2.4GHz Intel Core Duo, 4GB RAM. The PostgreSQL table containing those rows occupies less than 130 kb of disk space, and the queried rows comprise pretty much the entire table. Project info: 1 vector layer of polygons queried from a remote PostGIS database (query is simple and very fast) returning 160 total rows all in the project's defined coordinate space (WGS 84) and spanning the globe. Here's what I think is the relevant information for assessing whether it's performance is unusually slow. I am a new QGIS user and I am curious about how slowly it is performing it is possible that I'm asking more of it than I think I am.
0 kommentar(er)
