I am just wondering: Why is the "big" table only twenty rows? Is this a
multi(polygon?) table? If yes and the parts of each multipolygon are all
over the place then this is your problem. QGIS has to load all parts
although only a couple of them are visible at the moment. And if it
happens that
2016-06-24 5:40 GMT+02:00 Daniel Vicente Lühr Sierra :
> Hi,
>
> Indeed, 2.14.3 shows a better performance with respect to serving database
> data, even without yet tuning the database server.
>
>
Hello,
just a general consideration about testing QGIS server performances, you
Hi,
Indeed, 2.14.3 shows a better performance with respect to serving
database data, even without yet tuning the database server.
But, I still experience some performance issues. One, I detected when
using the print composer, which is very unresponsive if there is a map
object with a big
Hi Régis,
El 21/06/16 a las 10:37, Régis Haubourg escribió:
> Hi,
> please see that thread [0]
Thanks.
> I suggest you first upgrade qgis server to last 2.14.3.
Ok, some weeks ago I decided to stay with 2.8 ltr, until 2.14 was more
tested, it looks like it is time for upgrading.
> Then we still
Hi,
El 21/06/16 a las 10:35, Richard McDonnell escribió:
> Hi Daniel,
> Ok, so the first thing I would ask, is have you Indexed the geometry?
yes
> Secondly, If you are using any of the attributes for styling, I would
> also advise using Indexing on those also.
Not used in the testing data, but
Hi,
please see that thread [0]
I suggest you first upgrade qgis server to last 2.14.3.
Then we still have issues with big relational views, not tables - for first
getcapabilities generation (ie first load for a session).
You can also check your postgres logs to look at what queries are sent to
PG