Skip to main content
Solved

Patch Tool performance

  • June 24, 2026
  • 2 replies
  • 0 views

kyoung14
Varsity II
Forum|alt.badge.img

We have an internal test server.  Previously when I would run the PatchTool it updated within seconds.  Today I am running the newest version of the PatchTool against a 25R2 site.  It appeared to hang up on “Starting UI Compilation” but I let it run and it finally finished.  I then ran against another site and paid attention to the time.  It started the UI Compilation and 11:35 and didn’t finish the update until 11:47 (12 minutes).  Anyone else run into this?  Is this to be expected now?  You can see below that Node.js JavaScript Runtime was eating up most of the CPU.  Just curious if this is now normal.

 

 

Best answer by Dmitrii Naumov

@kyoung14 the previous patches did not have any UI changes in them, but this one does. Unfortunately with the UI patches it’s expected that there’ll be some time spent for UI rebuild. 

We are working on reducing this time, but it’ll not be zero for UI patches. Not every patch is going to have UI changes.

2 replies

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • Answer
  • June 24, 2026

@kyoung14 the previous patches did not have any UI changes in them, but this one does. Unfortunately with the UI patches it’s expected that there’ll be some time spent for UI rebuild. 

We are working on reducing this time, but it’ll not be zero for UI patches. Not every patch is going to have UI changes.


kyoung14
Varsity II
Forum|alt.badge.img
  • Author
  • Varsity II
  • June 24, 2026

@Dmitrii Naumov thank you for the response.  Good to know this may be normal at times.  As I said, it eventually finished but was so much longer than previously I just wanted to be sure there wasn’t an issue.