Author Topic: [Solved] Why is qb64 slow to open on my i7-6700 Win10 PC?  (Read 3998 times)

0 Members and 1 Guest are viewing this topic.

Offline Raptor88

  • Newbie
  • Posts: 22
    • View Profile
[Solved] Why is qb64 slow to open on my i7-6700 Win10 PC?
« on: April 13, 2019, 11:51:53 pm »
My desktop is running Win10 64bit on an i7-6700 CPU 3.4GHz, 16GB ram, 500GB system SSD (C:), 1.5TB HDD (D:)
My laptop is running Win10 64bit on an i7-6500U CPU 2.5GHz, 12GB ram, 256GB system SSD (C:), 1.0TB HDD (D:)

On my laptop, clicking QB64.exe on D: drive, it opens to the blue QB64 screen in 3 seconds.
On my desktop, clicking QB64.exe on D: drive, it opens to the blue QB64 screen in 11 seconds.
I copied the QB64 folder to the C: SSD drive and it still opens in 11 seconds.

The times above are on the second and subsequent openings of QB64.  When opening QB64 on my desktop, it stays on the black command screen for about 9 seconds and then it opens to the blue QB64 screen in 11 seconds.

Any ideas why my desktop opens QB64 so slowly?
« Last Edit: April 14, 2019, 09:40:58 am by odin »

Marked as best answer by Raptor88 on April 14, 2019, 01:29:32 am

FellippeHeitor

  • Guest
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #1 on: April 14, 2019, 12:02:43 am »
Antivirus getting in the way on the desktop?

Offline Raptor88

  • Newbie
  • Posts: 22
    • View Profile
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #2 on: April 14, 2019, 05:34:41 am »
Antivirus getting in the way on the desktop?
Wow Fellippe,

You nailed it.  Turning off BitDefender allows QB64 to open in about 2 seconds.
Now I have to figure out how to set QB64 as an exclusion in BitDefender.  My first attempts are not working.
But at least I know now what the problem is.

Thanks!
Raptor88

FellippeHeitor

  • Guest
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #3 on: April 14, 2019, 06:04:10 am »
Good to hear! :-)

Offline SMcNeill

  • QB64 Developer
  • Forum Resident
  • Posts: 3972
    • View Profile
    • Steve’s QB64 Archive Forum
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #4 on: April 14, 2019, 06:44:48 am »
Wow Fellippe,

You nailed it.  Turning off BitDefender allows QB64 to open in about 2 seconds.
Now I have to figure out how to set QB64 as an exclusion in BitDefender.  My first attempts are not working.
But at least I know now what the problem is.

Thanks!
Raptor88

https://www.bitdefender.com/support/how-do-i-exclude-a-folder-from-being-scanned-%5Bbitdefender-windows-8-security%5D-1067.html
https://github.com/SteveMcNeill/Steve64 — A github collection of all things Steve!

Offline Raptor88

  • Newbie
  • Posts: 22
    • View Profile
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #5 on: April 14, 2019, 07:07:13 am »
https://www.bitdefender.com/support/how-do-i-exclude-a-folder-from-being-scanned-%5Bbitdefender-windows-8-security%5D-1067.html

Thanks for your input.  I discovered why my exclusion was not working.  When I used the "Exclude File" option and excluded the QB64.exe file, the exclusion did not work.  When I use the "Exclude Folder" option and exclude the unzipped QB64 folder, then the exclusion works.

So now QB64 opens in about 2 seconds on my desktop with BitDefender running.

Thanks,
Raptor88

FellippeHeitor

  • Guest
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #6 on: April 14, 2019, 08:54:10 am »
That's because of the way QB64 works when running. The translation of BASIC code into C++ is restarted with every key you type into the IDE, which means it needs to rewrite the contents of several files multiple times. Then there's also compilation time when you hit F5 and then gcc is executed internally a few times as well as some of other utilities like the linker. That's why it's always a good idea to exclude the whole folder and subfolders from live scanning.

Offline Raptor88

  • Newbie
  • Posts: 22
    • View Profile
Re: Why is qb64 slow to open on my i7-6700 Win10 PC?
« Reply #7 on: April 14, 2019, 04:30:51 pm »
That's because of the way QB64 works when running. The translation of BASIC code into C++ is restarted with every key you type into the IDE, which means it needs to rewrite the contents of several files multiple times. Then there's also compilation time when you hit F5 and then gcc is executed internally a few times as well as some of other utilities like the linker. That's why it's always a good idea to exclude the whole folder and subfolders from live scanning.
Good to know info.  Thanks.