Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Deploying/Creating .Exe Slowdown

  1. Issue
0
Votes
Undo
  1. Michael Kniephof
    Michael Kniephof
  2. PowerBuilder
  3. Tuesday, 12 September 2023 22:57 PM UTC

Appeon Team,

Problem:

Creating the .exe when deploying a project has slowed down significantly.

Details:

PowerBuilder IDE Version 2019R3, build 2728.

When we’re deploying our projects/creating the .exe the "old way" (some of us aren’t using PowerClient deployment method yet), it now takes a really long time to create the .exe during the “Writing” phase. This started back in July shortly after we renewed our Appeon licenses (not sure if it's related to that or not).

During the “writing” phase I can open Windows File Explore to the location where the Executable file is built (C:\pbrepos\exes) and I can watch the .exe grow in size very slowly until it’s done. It used to take 60-90 seconds to create a 19,122 KB .exe. Now it takes up to 7 minutes.

I haven't been able to figure out what changed and why the .exe suddenly began to take so long. I've worked with the network and database teams to see if they knew of anything that changed but we couldn't find any issues.

Note, I checked with some other developers that I work with and they are experiencing the same issue.

I originally sent this to info@appeon.com and got a reply from Alejandro asking me to post the problem here and submit to New Bug (which I'll do next).

Let me know if I can provide other details that might help in figuring this out.

Thanks,

Mike K.

  1. .EXE
  2. Deployment
Getting TF31003 error when using TFS2012 connectin...
Why empty lines for autosize height field in previ...
Responses (3)
mike S
mike S Accepted Answer Pending Moderation
  1. Tuesday, 12 September 2023 23:18 PM UTC
  2. PowerBuilder
  3. # 1

see if disabling your anti-virus speeds things up.

Comment
Michael Kniephof
  1. Michael Kniephof
  2. Wednesday, 13 September 2023 15:22 PM UTC
This was it! Thank you so much for the idea. Anti virus never crossed my mind. I'll post more details below.
  1. Helpful 1
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 13 September 2023 05:28 AM UTC
  2. PowerBuilder
  3. # 2

EDIT: since you say that other developers are having the same issue, maybe all of the above doesn't make much sense.

Are you building a "Machine Code" executable? Check what happens if you build a P-code (PBD) executable. If that goes fast, then probably it has nothing to do with the licenses.

Check what significant code changes were made around the date of things slowing down.

That's all that crosses my mind for now.

regards.

Comment
There are no comments made yet.
Michael Kniephof
Michael Kniephof Accepted Answer Pending Moderation
  1. Wednesday, 13 September 2023 15:29 PM UTC
  2. PowerBuilder
  3. # 3

At the suggestion of mike S I figured out that it was indeed our anti virus software causing the problem.

We started using CrowdStrike Falcon anti virus recently. I couldn't even disable it myself. Our helpdesk team had to do a special uninstall. Now we need to submit a ticket with CrowdStrike to see if whitelisting (perhaps PB190.exe?) will fix it going forward.

Thanks mike s and Miguel Leeuwe for your quick responses!

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 13 September 2023 16:11 PM UTC
Hi Michael;

Thank you so much for confirming that your AV was the issue!



TIP: This also what I use on my PB IDE machines in my PB.INI, as follows ...

[PB]

; Target the output of your Machine Code compiles to a specific location (IDE Only). For example ...

CODEGENTEMP=G:\PB\CplusPlus



In my case, I force the compilation process to use my "G" drive which is a *super fast* SSD. This cuts my STD framework compiles down by better than 50%. Food for thought. HTH



Regards ... Chris
  1. Helpful
Daryl Foster
  1. Daryl Foster
  2. Thursday, 14 September 2023 00:05 AM UTC
Hi Michael,



I had the same problem recently with Crowdstrike Falcon. Our system administrator was able to add an exclusion zone on my machine to the project directory where I compile my application. Below are some comments from my system administrator that you can pass onto your helpdesk administering Crowdstrike to see if it helps:



In the dashboard they need to go under Endpoint Security -> Exclusions



Add a Exclusion for the folder and child objects with syntax "Source\MyApplication\** "



And set Exclusion Type to Exclude Detections and Preventions and Exclude Uploads to Crowdstrike
  1. Helpful 2
Michael Kniephof
  1. Michael Kniephof
  2. Thursday, 14 September 2023 15:17 PM UTC
Thank you Daryl. I will pass that information along and I'm sure it will be helpful.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.