Just how low should you go ? Or expect too.

[doppler]

While at work, I use a personal machine (core2 Duo) sometime to do little things with Qb64.
I never really paid attention just how much processor % was being used.  Until today
Win 10 decided to do some other things too.  The core2 is not bottom end, neither is it
high end.  While win 10 was doing it's thing.  I really could not use the QB64 IDE.  It was
too laggy.  When things later got better, I checked how much time QB64 spent in the IDE
doing nothing.  From 3-6% bouncing, to 33%-40% (all over) in QB64 IDE.

Just wondering now how lowly a processor should be used with QB64 ?  I have retired
and dismantled anything less than that Core2.  At home my I7 doesn't even give it a blip.

Or has the V1.3 IDE have some hidden excessive cycles being eaten somewhere ?

[Bert22306]

Not answering your question, but to give another data point. Version 1.3 IDE open, in my Core i5 laptop, is bouncing around 0.3% to 0.7%, occasional peak at 1%, for CPU loading. And bouncing between 0% and 7.9% for GPU loading.

[doppler]

A little more:
The Core2 processor is 3.0ghz running in x64 win 10.  I got more than needed ram at 4GB.
One of the two cores (no hyper's) is running at 50%, the other is 20-40%.

In the past when processor cycles were excessive things were found.  There could be things
to be found now too.  Could be something as simple as a do loop without a limit set somewhere.

Tools to check and test program code for flow efficiency are complex and expensive.  Sometimes
they are needed to be developed in-house.  How many buckets of cash do you think developers
for QB64 get ?  I'd say zero to negative.
 

[Jack002]

Before QB64 in the days of quickbasic, that IDE would be a processor hog. Just sitting there it would slow the computer way down.
I'm on QB64 v1.2 and see no slowness here.