Hi Alberto,
Startup time with a blank project is 30 seconds here with Kaspersky security
ON.
With Kaspersky turned off, start up time is still 28 seconds - barely any
difference.
Kaspersky is generally known for being a quite low overhead.
--
Sent from:
Hi all,
I don't know if this is has already been brought forward: on Windows 10, at
least for me, the antivirus service vastly increases the QGIS loading
times. I did a quick test today (I have got more than 20 plugins installed
and active):
- AV disabled: loading time 23 secs
- AV enabled:
Hi Nyall,
In answer to your query, all my files are held on my desktop PC, with specs
as follows:
CPU: Intel Core i7-4790K
GPU: Nvidia Quadro K2200
SSD: Samsung 840 Evo 250GB
HDD: Seagate Barracuda 7200.14 2TB
HDD: Seagate Barracuda 7200.14 2TB
USB: WD My Book 1230 4TB
RAM: Corsair
Hi Nyall -
You scored a bullseye on that - I've done some testing
- Startup with all plugins activated: *28* seconds
- Startup with processing plugin deactivated : *19* seconds
- Startup with proccessing and "Kortforsyningen" plugins deactivated -
*11* seconds
(Test done on my 2.
Sorry for that, my mistake
Easy one to make, however, when you have four Linux PCs to do the work
on and one token Windows PC that is unused most of the time these days.
On 14/12/18 10:50 PM, Nyall Dawson wrote:
On Fri, 14 Dec 2018 at 11:36, Patrick Dunford wrote:
As far as I know,
BINGO! That’s a lot faster startup!
> My guess is that the initialization of the python plugins runs very, very
> slow on the Windows pc. So the culprit may be the python interpreter on
> Windows.
This sounds like a known issue since ages (v 2.6?), where at QGIS
startup the Processing plugin
On Mon, 17 Dec 2018 at 18:49, David Addy wrote:
>
> Hi Nyall,
> Thanks for your additional comment.
> When I was autoloading my most recent project at startup QGIS was taking up
> to a minute to open itself and load the project. Other saves and actions
> like opening a layer attribute table were
On Mon, 17 Dec 2018 at 20:10, Bo Victor Thomsen
wrote:
>
> Just my - very late – 2 cents.
>
>
>
> I have 2 computers that is exactly the same type: Lenovo Thinkpad P50. There
> is no difference in cpu, memory, SSD or graphics. One is running Windows 7
> and one is running Ubuntu 18.04. Both
Just my - very late – 2 cents.
I have 2 computers that is exactly the same type: Lenovo Thinkpad P50.
There is no difference in cpu, memory, SSD or graphics. One is running
Windows 7 and one is running Ubuntu 18.04. Both have QGIS 3.4.2 with the
same plugins installed.
The Linux pc starts
Hi Nyall,
Thanks for your additional comment.
When I was autoloading my most recent project at startup QGIS was taking up
to a minute to open itself and load the project. Other saves and actions
like opening a layer attribute table were also very slow.
After changing my settings to open with a new
On Sun, 16 Dec 2018 at 08:51, David Addy wrote:
>
> Thanks to everybody, but to Anita and Nyall in particular, for your comments.
> It is very helpful to know that my issues are just minor quirks rather than
> a more serious flaw.
Sorry David -- I wasn't meaning to say that the issues you're
Thanks to everybody, but to Anita and Nyall in particular, for your comments.
It is very helpful to know that my issues are just minor quirks rather than
a more serious flaw.
QGIS 3 is definitely a big leap forward and I can now plough onwards with
these reassurances.
I would rather avoid going to
On Fri, 14 Dec 2018 at 11:36, Patrick Dunford wrote:
>
> As far as I know, development is done mainly in Linux
>
> The Windows and Mac editions are ports off this. I am sure the
> developers and port teams do their best but you can run into issues that
> are platform specific and are hard to
Hi,
I'm using QGIS on Windows a lot and cannot confirm issues with slow startup
in 3.4. The Windows version is consistently on par with the Linux version.
(Notable exceptions in version 2 were the globe extension and R support
which I couldn't get to work back then.)
The incorrect description of
As far as I know, development is done mainly in Linux
The Windows and Mac editions are ports off this. I am sure the
developers and port teams do their best but you can run into issues that
are platform specific and are hard to resolve. Particularly as it is
dependent on third party libraries
Hi Patrick,
Thanks for your comments. It all helps to encourage me.
I have now discovered that the User Manual (development version) emphasises
the fact that there are changes to the node tool in version 3, and how the
dragging of the old method is now replaced by two clicks. Anita's book does
not
I run the latest 3.4.x on Linux which has been very stable and reliable.
It will be a while before 3.x is as mature and dependable as 2.x which
was at 2.18 a very mature product that had been operating a good number
of years.
Used to run the development version 2.99 but these days I view
If you have enough resources running it in a VM is an option and can be
a linux version, very stable and very resource efficient
I used to have a bg stack of VMs running all sorts of versions when I
used to run the development version more than I do now, it was almost
seamless
On 11/12/18
Plenty of bugs are being discovered and reported but not many bug
reports are being opened, as it appears to me.
I'm not aware of issues with the new node editor. It works very well
most of the time.
Qgis 3.4.anything is very stable on Debian, I stopped running it on
Windows a long time
Thanks for all your comments. I think things were pretty good using 3.2, and
I had got used to using Version 3 with geopackage etc, and going back to
2.18 was rather painful for me. These hanging up problems for me really
started in 3.4.
I have just found that changing my Settings to make QGIS
I can report that I do not see the same thing reported
below. I use QGIS 3.2.0 on Win7 with a pretty good graphics
card and I don't have any problems at all. I'm thinking it
has perhaps froze up a couple times since the install in late
June 2018, but I don't recall the last time that happened.
Saber Razmjooei wrote
> On Tue, 11 Dec 2018 at 10:39, Antongeo76
> antoviscomi@
> wrote:
>
>> berndv. wrote
>> > Hi,
>> >
>> > I can't contribute to your particular problems, but have some remarks.
>> >
>> > You said you "reverted" to 2.18. On Windows, you can easily run 3.x
>> > besides 2.x.
-
Antonio
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe:
On Tue, 11 Dec 2018 at 10:39, Antongeo76 wrote:
> berndv. wrote
> > Hi,
> >
> > I can't contribute to your particular problems, but have some remarks.
> >
> > You said you "reverted" to 2.18. On Windows, you can easily run 3.x
> > besides 2.x. Do you have the same problems with 2.18? If so,
berndv. wrote
> Hi,
>
> I can't contribute to your particular problems, but have some remarks.
>
> You said you "reverted" to 2.18. On Windows, you can easily run 3.x
> besides 2.x. Do you have the same problems with 2.18? If so, it's
> really your personal installation that fails, I think.
>
Saber Razmjooei wrote
> It's been said a lot and often gets dismissed by users (similar to have
> you
> turn off and on your computer), but most of the issues can be resolved by:
> 1- Start your QGIS 3, with a clean profile.
> 2- Remove/disable all 3rd party plugins
>
> If all fails, report the
It's been said a lot and often gets dismissed by users (similar to have you
turn off and on your computer), but most of the issues can be resolved by:
1- Start your QGIS 3, with a clean profile.
2- Remove/disable all 3rd party plugins
If all fails, report the bug with a sample data and
Hi,
I can't contribute to your particular problems, but have some remarks.
You said you "reverted" to 2.18. On Windows, you can easily run 3.x
besides 2.x. Do you have the same problems with 2.18? If so, it's
really your personal installation that fails, I think.
The node tool was
David Addy wrote
> I have always loved QGIS and I have extolled its virtues to local
> historians
> and archaeologists in my area.
> I have had to keep quiet about it lately.
> I was somewhat relieved to hear a comment on a recent video of the Oceania
> meeting that QGIS 3.4.1 was a dud release as
I have always loved QGIS and I have extolled its virtues to local historians
and archaeologists in my area.
I have had to keep quiet about it lately.
I was somewhat relieved to hear a comment on a recent video of the Oceania
meeting that QGIS 3.4.1 was a dud release as it caused Windows to crash
30 matches
Mail list logo
