I'm using QGIS to build complex maps from OSM-Data (GPKG or PostGIS). I'm wondering, how I should upgrade my system, to speed up rendering in canvas:

Intel I5 4x3,2GHz, 16GB DDR3, SSD

Or what about using RAM-Disk or RAID?

In the GIF-Animation you can see real time rendering at changing scale: https://media.giphy.com/media/MUlt8lb1iuzm80alyE/giphy.gif 2 or more seconds for every canvas move or scale are just too much for a smooth work.

I already use parallel rendering for all CPU and simplification: enter image description here

  • Maybe it will improve if you use the maximum number of cores – Fran Raga May 11 '19 at 12:08
  • 1
    I think that other checkbox ("max cores to use") is for limiting the number of cores. It looks like the default is to use all available cores (or at least, what Qt thinks is the ideal number). Have you tried enabling the "debugging" checkbox at the bottom of that dialog? It adds a tab to the Log panel which shows rendering times for each individual layer. – Steven Kay May 11 '19 at 18:54
  • Dell has tool called workstation advisor that will recommend a (new) hardware setup based on what you plan to do with it. You can compare the specs of their recommendations to what you currently have to get a general sense of where your system falls short. The Intel i5 is old enough that you can get a substantial upgrade by buying a refurbished computer in the $200-$400 price range. – csk May 13 '19 at 16:28

Probably a bit off topic but, before investing in to hardware I suggest you first look into Postgres/PostGIS tunning. Some starting points:

Tuning PostGIS for production environments?

Performance Tuning PostgreSQL

Tuning Your PostgreSQL Server

PostGIS preformance tips

Tunning PostgreSQL on your Dedicated Server

From my experience you can greatly improve rendering preformance by increasing simplification treshold:

enter image description here

Its not clear data structure of your maps, I presume you have several layers for roads, contours, coverage etc... Reducing tables might help as well since "Overall storage is practically always (substantially) cheaper with a single table instead of multiple tables in 1:1 relationship." (@Erwin Brandstetter). You could achiev this by creating views for layers with same geometry.

If none of this helps enough start thinking of hardware.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.