I'm currently reporting an issue our users are facing in the field. We are using QGIS / PostgreSQL to collect data on daily basis and since few weeks they are noticing a huge difference in performances with QGIS. For instance: henceforth it takes for them approximatively 10 secondes to open a single form where it took QGIS just half a second to open it at the beginning (3 months ago). All the QGIS process is slowing down, which is delaying their job and creating issues... they can't afford to wait for the "tablet" in their duty. They are working on a Microsoft surface pro (i5, 4Go, 128Go SSD) bought in October to replace a previous tablet which was way less performant. At the beginning, the combo surface pro/ QGIS was working extremely well, with high level of performance and reactivity. The tablet is completely offline, no updates, no connection with internet, no system modifications since the first use. It appears all the others "windows tasks" they need to do (running scripts, opening softwares) are working without any loose of performance so far. Our QGIS project contains 6 layers, some with geometry, which are only use to open and fill forms in order to fill the database stored in PostgreSQL. The amount of data they have to enter on daily basis didn't change from the time they received the surface pro. According to web solutions, we : - unselected all plugins and check : no difference - selected "show markers only for selected features" and check : no difference Hence I'm running out of solutions and I'll plan to migrate back to a more stable version like 2.14 and see what it does. Have you ever experience such a problem and/or would you have some tracks to follow ? --- before installing the new version of Qgis (actually I was planning to change it to the 2.16), I tried to create a new project and it worked. From the feedbacks of the users when we just done it, it seems to be as fast as the beginning for the moment. Nevertheless, we need to wait and see few days before clapping hands.. But why would it have solved the issue ? any idea/suggestions ? Simple bug ?