Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #12349 > unrolled thread

Very slow debugging and compiling

Started bygrzd.petrovic@gmail.com
First post2019-03-25 06:55 -0700
Last post2019-04-11 01:07 -0700
Articles 15 — 8 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Very slow debugging and compiling grzd.petrovic@gmail.com - 2019-03-25 06:55 -0700
    Re: Very slow debugging and compiling "Wolfgang Riedmann" <wriedmann@gmail.com> - 2019-03-25 16:35 +0100
      Re: Very slow debugging and compiling grzd.petrovic@gmail.com - 2019-03-25 09:11 -0700
        Re: Very slow debugging and compiling "Wolfgang Riedmann" <wriedmann@gmail.com> - 2019-03-25 20:16 +0100
    Re: Very slow debugging and compiling "Jean3Riv@gmail.com" <jean3riv@gmail.com> - 2019-03-26 05:00 -0700
      Re: Very slow debugging and compiling grzd.petrovic@gmail.com - 2019-03-26 12:20 -0700
      Re: Very slow debugging and compiling D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2019-04-02 23:03 +0200
    Re: Very slow debugging and compiling grzd.petrovic@gmail.com - 2019-04-10 04:10 -0700
      Re: Very slow debugging and compiling "Jamal" <noooospam@example.com> - 2019-04-10 14:27 -0400
        Re: Very slow debugging and compiling grzd.petrovic@gmail.com - 2019-04-11 01:06 -0700
          Re: Very slow debugging and compiling "Jamal" <noooospam@example.com> - 2019-04-11 20:57 -0400
            Re: Very slow debugging and compiling francka.kmet@gmail.com - 2019-04-15 00:51 -0700
              Re: Very slow debugging and compiling "Jamal" <nospam@example.com> - 2019-04-15 14:49 -0400
      Re: Very slow debugging and compiling Chris Pyrgas <"chris (at)"@xsharp.eu> - 2019-04-10 21:46 +0300
        Re: Very slow debugging and compiling grzd.petrovic@gmail.com - 2019-04-11 01:07 -0700

#12349 — Very slow debugging and compiling

Fromgrzd.petrovic@gmail.com
Date2019-03-25 06:55 -0700
SubjectVery slow debugging and compiling
Message-ID<a3b44c9e-d672-4db8-af55-3925d44d0a4c@googlegroups.com>
Hello!

I finally transferred my VO development environment from XP to Windows10 64 bit machine (4GB RAM, Ryzen 5, 6 cores, 3,2GHz) and got immediately faced with the problem I cannot solve by myself.

Compiling and debugging times become significantly longer on the new machine although the new machine is faster than the old one.

For example:
- compiling time of the whole application (all entities touched) is 250 seconds on the new machine in comparison to 30 seconds on the old machine  
- debugging: just to start the application in debug mode it takes 10 seconds with 1 breakpoint set, whereas on the old machine took only 2 seconds. 
If I add additional breakpoints, the start time grows linearly, that is with each breakpoint set, start time becomes 10 seconds longer. With 7 breakpoints set it takes 70 seconds just to start the application.

Memory usage is at around 38%. All other applications are closed. CPU load is at 9-12%.

All other applications work fine (MS Office, internet browsers....), therefore I believe the hardware is not the issue.
All the VO environmental variables and settings are the same as on the old machine.
I use CAVO 2.8 Sp2 build 2830.
All maps have administrator rights and I am logged as a member of the administrator group. There are 2 SSD disks in the machine, CAVO binaries are on the disk 1, program data (source code, libraries…) on the disk 2.
I have already exported, deleted, imported and re-indexed the project several times.

Any thoughts or directions?

Gorazd

[toc] | [next] | [standalone]


#12352

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2019-03-25 16:35 +0100
Message-ID<gfsaqnF2nb4U1@mid.individual.net>
In reply to#12349
Hi Gorazd,

unfortunately I cannot give you any advice. I'm working on a Windows 10
machine for years now, but with a dual core Intel i7 2,8 Ghz.
Your memory seems to be small for a 64 bit development machine, I would
put in at least 8 GB if not more (my machine has 16 GB).

VO does not uses more than one core, so it will not take any advance
from multi-core processors, but the only thing that counts is the
single core performance.

I would check the antivirus settings, maybe there is something not
working well.

The only issue I have with Windows 10 is that sometimes the ressource
compiler does not works anymore, and I need to restart all VO instances.

And yes, I'm using VO 2.8 2838 (SP4b).

Wolfgang


grzd.petrovic@gmail.com wrote:

> Hello!
> 
> I finally transferred my VO development environment from XP to
> Windows10 64 bit machine (4GB RAM, Ryzen 5, 6 cores, 3,2GHz) and got
> immediately faced with the problem I cannot solve by myself.
> 
> Compiling and debugging times become significantly longer on the new
> machine although the new machine is faster than the old one.
> 
> For example:
> - compiling time of the whole application (all entities touched) is
> 250 seconds on the new machine in comparison to 30 seconds on the old
> machine - debugging: just to start the application in debug mode it
> takes 10 seconds with 1 breakpoint set, whereas on the old machine
> took only 2 seconds.  If I add additional breakpoints, the start time
> grows linearly, that is with each breakpoint set, start time becomes
> 10 seconds longer. With 7 breakpoints set it takes 70 seconds just to
> start the application.
> 
> Memory usage is at around 38%. All other applications are closed. CPU
> load is at 9-12%.
> 
> All other applications work fine (MS Office, internet browsers....),
> therefore I believe the hardware is not the issue.  All the VO
> environmental variables and settings are the same as on the old
> machine.  I use CAVO 2.8 Sp2 build 2830.  All maps have administrator
> rights and I am logged as a member of the administrator group. There
> are 2 SSD disks in the machine, CAVO binaries are on the disk 1,
> program data (source code, libraries…) on the disk 2.  I have
> already exported, deleted, imported and re-indexed the project
> several times.
> 
> Any thoughts or directions?
> 
> Gorazd



-- 

[toc] | [prev] | [next] | [standalone]


#12354

Fromgrzd.petrovic@gmail.com
Date2019-03-25 09:11 -0700
Message-ID<6eb12bcd-acd3-42df-ac66-73077a3c123e@googlegroups.com>
In reply to#12352
Thanks for the answer Wolfgang!

I plan to upgrade RAM anyhow, although I doubt RAM is a reason for such behavior (only 38% usage).
The only antivirus software that is currently installed is Windows defender (internal Win10 antivirus). I have disabled it, but unfortunately no improvement hasn’t been noticed. 
I checked with my colleague who is also using Windows 10 and the same version of VO (2830 SP2) and he is also not experiencing any kind of problems mentioned above. 

BTW where could I get 2838 SP4 version of VO?

Gorazd.

[toc] | [prev] | [next] | [standalone]


#12355

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2019-03-25 20:16 +0100
Message-ID<gfsnodF5gq1U1@mid.individual.net>
In reply to#12354
Hi Gorazd,

> I plan to upgrade RAM anyhow, although I doubt RAM is a reason for
> such behavior (only 38% usage).  The only antivirus software that is
> currently installed is Windows defender (internal Win10 antivirus). I
> have disabled it, but unfortunately no improvement hasn’t been
> noticed.  I checked with my colleague who is also using Windows 10
> and the same version of VO (2830 SP2) and he is also not experiencing
> any kind of problems mentioned above.

I'm too using the integrated Windows Defender, after having used Trend
Micro Business Antivirus for years.
Do you have freshly installed VO?

But Windows uses all available memory caching, so this could make a
difference.

Compiling is a lot of read/write processes, so your disk could be a
bottleneck

> BTW where could I get 2838 SP4 version of VO?

unfortunately GrafX has decided to close down their company, and an
unofficial page to buy an upgrade could be this one here:
http://www.visualobjects.net/
I'm not sure if you get a regular license, since GrafX is closed, and
the license agreement with Computer Associates, the copyright owner of
Visual Objects, may have been expired.

Wolfgang

-- 

[toc] | [prev] | [next] | [standalone]


#12361

From"Jean3Riv@gmail.com" <jean3riv@gmail.com>
Date2019-03-26 05:00 -0700
Message-ID<91c6076e-5ff2-408b-8930-beeac26f1411@googlegroups.com>
In reply to#12349
On Monday, March 25, 2019 at 9:55:37 AM UTC-4, grzd.p...@gmail.com wrote:
> Hello!
> 
> I finally transferred my VO development environment from XP to Windows10 64 bit machine (4GB RAM, Ryzen 5, 6 cores, 3,2GHz) and got immediately faced with the problem I cannot solve by myself.
> 
> Compiling and debugging times become significantly longer on the new machine although the new machine is faster than the old one.
> 
> For example:
> - compiling time of the whole application (all entities touched) is 250 seconds on the new machine in comparison to 30 seconds on the old machine  
> - debugging: just to start the application in debug mode it takes 10 seconds with 1 breakpoint set, whereas on the old machine took only 2 seconds. 
> If I add additional breakpoints, the start time grows linearly, that is with each breakpoint set, start time becomes 10 seconds longer. With 7 breakpoints set it takes 70 seconds just to start the application.
> 
> Memory usage is at around 38%. All other applications are closed. CPU load is at 9-12%.
> 
> All other applications work fine (MS Office, internet browsers....), therefore I believe the hardware is not the issue.
> All the VO environmental variables and settings are the same as on the old machine.
> I use CAVO 2.8 Sp2 build 2830.
> All maps have administrator rights and I am logged as a member of the administrator group. There are 2 SSD disks in the machine, CAVO binaries are on the disk 1, program data (source code, libraries…) on the disk 2.
> I have already exported, deleted, imported and re-indexed the project several times.
> 
> Any thoughts or directions?
> 
> Gorazd

Hello all...

I have the same problem too, in the debug mode!!!

My PC Operating system:     Windows 10 Pro (x64)    Version: 1809   Build: 17763.379

I have CAVO 2.8 SP3

In debug mode it is crawling, as a work around I use only the debug mode
on module I’m working on.

Another work around is that I use Oracle Virtual boxe, and I installed
Windows 8.1. And now everything is working like a charm (very fast in debug
mode and also in regular mode)

Then I say to myself, it is Windows 10 the problem.

Then I tried the latest windows 10 insider fast track Version 1903 build 18362.1
in another Oracle Virtual box.
The result is the speed has came back

So my humble conclusion...

Wait few days or weeks, windows 10 version 1903 will go out very soon

This will resolve the problem (I HOPE)

Best regards

Jean Raymond
https://rayonline.com

[toc] | [prev] | [next] | [standalone]


#12363

Fromgrzd.petrovic@gmail.com
Date2019-03-26 12:20 -0700
Message-ID<0e24d267-2682-4518-8a76-f54d88d58d9c@googlegroups.com>
In reply to#12361
Hi Jean,

If it is “just” Windows, I am ready to wait till the new version is officially released.

Have you tried a clean install of Windows Version: 1809   Build: 17763.379 (the one you are using at the moment in production environment) in the virtual machine? Maybe it is not a Windows version, maybe it has something to do with Windows configuration which was very probably not the same in the virtual machine (version 1903) compared to the version 1809 in production environment?

Meanwhile I am waiting for the RAM extension which I ordered today. Maybe the upgrade from 4GB to 16GB will help.

Gorazd

[toc] | [prev] | [next] | [standalone]


#12383

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2019-04-02 23:03 +0200
Message-ID<o4j7ae1m7tcden30ko3b4vvqqvh5ht0qp8@4ax.com>
In reply to#12361
Replying on message of Tue, 26 Mar 2019 05:00:38 -0700 (PDT) from
Jean3Riv@gmail.com:


 Hello Jean,

>So my humble conclusion...
>
>Wait few days or weeks, windows 10 version 1903 will go out very soon
>
>This will resolve the problem (I HOPE)
>
Windows 10 feature releases NEVER solve existing problems. The chance
is much higher that it creates one or more problems. As you may
remember the 1809 had to be withdrawn because copying files in
Explorer could either overwrite or not copy at all existing files. 

Feature releases are released to add a bunch of new features nobody is
waiting for. Which can disbable functionality - even if it has worked
all right for the last 20 years ot so, like the above Explorer issue.
They are not solving problems; this is supposed to be done in the more
regular interim releases and it sometimes does.

I have about the same configuration as Wolfgang and it works fine,
speedwise. You really have to investigate settings, virus scanners,
running processes and more. These you should find the cause.

I strongly recommend against directly installing a W10 feature upgrade
in a production environment. Wait at least a few months until the
worst bugs are solved.

Dick

[toc] | [prev] | [next] | [standalone]


#12414

Fromgrzd.petrovic@gmail.com
Date2019-04-10 04:10 -0700
Message-ID<da9c27f0-df33-4a4a-bb4c-a9767b04ebe6@googlegroups.com>
In reply to#12349
Hello Jean and Dick,

A follow up from my side:

1.	Installation of additional RAM (16 GB altogether) does not solve the problem

2.	I installed a new version of Win10 (Version 1903 build 18362.30) on the new machine (real computer - not virtual machine, installation of win10 from the scratch and later upgraded via win preview, disk formatted, all default drivers, fresh installation of CAVO, libraries and project imported via AEF files… ) and I can confirm that for me it doesn't solve the problem. The same slow execution under debugging is still present. 

So I have to join Dick's opinion, that it is not a problem in old/new win10 version, but somewhere else.  If I am honest I don't know how to proceed with this, so any idea or suggestion will be appreciated.

Gorazd.

[toc] | [prev] | [next] | [standalone]


#12415

From"Jamal" <noooospam@example.com>
Date2019-04-10 14:27 -0400
Message-ID<q8lcio$v7r$1@news.albasani.net>
In reply to#12414
CAVO.exe is a 32bit program and cannot utilize virtual memory above 2GB. If 
you want VO to become large address aware on 64bit Windows, you can try can 
https://ntcore.com/?page_id=371.

** Make sure you backup the CAVO folder before proceeding. **

There was a discussion a few months ago about this in the X# forum and I 
created a X# version. In my own installation programs, I created a C# 
terminal app to patch 32bit .exe files and I have not had any issues.
Discussion here: 
https://www.xsharp.info/forum/public-vo-vn/758-vo-32-bit-limitations?start=0

Hopefully this will help you.

Jamal

wrote in message 
news:da9c27f0-df33-4a4a-bb4c-a9767b04ebe6@googlegroups.com...

Hello Jean and Dick,

A follow up from my side:

1. Installation of additional RAM (16 GB altogether) does not solve the 
problem

2. I installed a new version of Win10 (Version 1903 build 18362.30) on the 
new machine (real computer - not virtual machine, installation of win10 from 
the scratch and later upgraded via win preview, disk formatted, all default 
drivers, fresh installation of CAVO, libraries and project imported via AEF 
files… ) and I can confirm that for me it doesn't solve the problem. The 
same slow execution under debugging is still present.

So I have to join Dick's opinion, that it is not a problem in old/new win10 
version, but somewhere else.  If I am honest I don't know how to proceed 
with this, so any idea or suggestion will be appreciated.

Gorazd. 

[toc] | [prev] | [next] | [standalone]


#12418

Fromgrzd.petrovic@gmail.com
Date2019-04-11 01:06 -0700
Message-ID<84d29003-3447-4094-b237-6803a3971ed5@googlegroups.com>
In reply to#12415
Hi Jamal,

thanks for the info. However problem is not with the amount of memory that CAVO can use. 16 GB extension was meant to improve (and maybe in the same time solve the debugging problem) the responsiveness of IDE environment. During the development process there are usually many applications open (IDE itself, browsers, editors……) which use RAM, and the idea was to eliminate possible extensive disk swapping due to the lack of RAM.

I have never had a problem with my application. It runs perfectly fine when outside of IDE. And it runs fine in the IDE as well, provided that it is not running with Debug – F5.

But with debug it runs terribly slow. It feels like as with each debug step there is an empty  loop executed which does nothing but eats time. The more entities are marked with debug setting on, the longer is the execution time. If all modules are marked with debug property on, the IDE (debugging) becomes so slow that normal work is not possible any longer. During this time there is practically no disk activity, CPU load is low and there is still plenty RAM available. All other open applications (browser, editors….) are unaffected. The Internal MS virus defender is turned off and no other anti-virus software is used.

The same application in the same CAVO IDE version on XP runs perfectly fine.

Gorazd

[toc] | [prev] | [next] | [standalone]


#12422

From"Jamal" <noooospam@example.com>
Date2019-04-11 20:57 -0400
Message-ID<q8onps$u61$1@news.albasani.net>
In reply to#12418
Hi Gorazd,

Open Windows Task Manager (either on a 2nd monitor or keep on top) and see 
if the CAVO28.exe becomes "Suspended" in the Status column.


Jamal

wrote in message 
news:84d29003-3447-4094-b237-6803a3971ed5@googlegroups.com...

Hi Jamal,

thanks for the info. However problem is not with the amount of memory that 
CAVO can use. 16 GB extension was meant to improve (and maybe in the same 
time solve the debugging problem) the responsiveness of IDE environment. 
During the development process there are usually many applications open (IDE 
itself, browsers, editors……) which use RAM, and the idea was to eliminate 
possible extensive disk swapping due to the lack of RAM.

I have never had a problem with my application. It runs perfectly fine when 
outside of IDE. And it runs fine in the IDE as well, provided that it is not 
running with Debug – F5.

But with debug it runs terribly slow. It feels like as with each debug step 
there is an empty  loop executed which does nothing but eats time. The more 
entities are marked with debug setting on, the longer is the execution time. 
If all modules are marked with debug property on, the IDE (debugging) 
becomes so slow that normal work is not possible any longer. During this 
time there is practically no disk activity, CPU load is low and there is 
still plenty RAM available. All other open applications (browser, editors….) 
are unaffected. The Internal MS virus defender is turned off and no other 
anti-virus software is used.

The same application in the same CAVO IDE version on XP runs perfectly fine.

Gorazd 

[toc] | [prev] | [next] | [standalone]


#12426

Fromfrancka.kmet@gmail.com
Date2019-04-15 00:51 -0700
Message-ID<e6d4fc23-247a-48ac-9e41-01657f3c02fb@googlegroups.com>
In reply to#12422
Hi Jamal,

sorry for the delayed answer, I was away for a few days.
I made the observation of both processes:
- cavo28.exe (IDE process)
- and MyProgram.DBG (debugg process started within IDE)

None of them shows any kind of "strange" data in task manager.
Status is Running (not Suspended), CPU below 8%, peak working memory below 100 Mb, disk active time below 1%.
However there is a substantial number of accumulated "page faults" 98.000, which I do not know the meaning of.
I/O reads and I/O writes are also high compared to other processes, but I assume this is normal since debugging process is quite I/O intensive. 

Gorazd

[toc] | [prev] | [next] | [standalone]


#12429

From"Jamal" <nospam@example.com>
Date2019-04-15 14:49 -0400
Message-ID<q92jno$5tr$1@gioia.aioe.org>
In reply to#12426
You can google about the page faults, but from what I read it mostly has to 
do with lack of memory to the process which causes many page faults.

wrote in message 
news:e6d4fc23-247a-48ac-9e41-01657f3c02fb@googlegroups.com...

Hi Jamal,

sorry for the delayed answer, I was away for a few days.
I made the observation of both processes:
- cavo28.exe (IDE process)
- and MyProgram.DBG (debugg process started within IDE)

None of them shows any kind of "strange" data in task manager.
Status is Running (not Suspended), CPU below 8%, peak working memory below 
100 Mb, disk active time below 1%.
However there is a substantial number of accumulated "page faults" 98.000, 
which I do not know the meaning of.
I/O reads and I/O writes are also high compared to other processes, but I 
assume this is normal since debugging process is quite I/O intensive.

Gorazd 

[toc] | [prev] | [next] | [standalone]


#12416

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2019-04-10 21:46 +0300
Message-ID<q8ldkg$1e2q$1@gioia.aioe.org>
In reply to#12414
Hi Gorazd,

I would start by completely disabling my Antivirus temporarily, to see 
if that makes a difference.

If that doesn't help, I would look in the taks manager every one of the 
processes running, maybe one of them is using CPU time. Or maybe one is 
using the disk extensively (even if it is a SSD), causing such delays.

hth,
Chris

> Hello Jean and Dick,
>
> A follow up from my side:
>
> 1.	Installation of additional RAM (16 GB altogether) does not solve the problem
>
> 2.	I installed a new version of Win10 (Version 1903 build 18362.30) on the new machine (real computer - not virtual machine, installation of win10 from the scratch and later upgraded via win preview, disk formatted, all default drivers, fresh installation of CAVO, libraries and project imported via AEF files… ) and I can confirm that for me it doesn't solve the problem. The same slow execution under debugging is still present.
>
> So I have to join Dick's opinion, that it is not a problem in old/new win10 version, but somewhere else.  If I am honest I don't know how to proceed with this, so any idea or suggestion will be appreciated.
>
> Gorazd.
>

[toc] | [prev] | [next] | [standalone]


#12419

Fromgrzd.petrovic@gmail.com
Date2019-04-11 01:07 -0700
Message-ID<1c1a2470-ec7c-48c5-be98-8c87629e1144@googlegroups.com>
In reply to#12416
Hi Chris,

thanks for the answer. 
I will try to do it by the elimination method, although looking at the processes and their activity everything looks normal. Are there maybe any hidden processes that can be shown with some windows option turned on?

Please see my reply to Jamal as well.

Gorazd

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web