AEM slow down when copy node | Community
Skip to main content
rohitm58172886
Level 2
July 4, 2019
Solved

AEM slow down when copy node

  • July 4, 2019
  • 12 replies
  • 5978 views

Hi,

     Programatically,I am copy some nodes(source node) and paste it on under parent node(destination node).When this process executing AEM consume more cpu usage its nearly goes 90% so AEM Slow down.

Code

          import javax.jcr.Session;

          import javax.jcr.Workspace;

          import org.apache.sling.jcr.api.SlingRepository;

          .

          /**************Some Code**************/

               Session session = repository.loginAdministrative(null);

               Workspace ws = session.getWorkspace();

               ws.copy(sourceNodepath, ParentNodepath);

          /***********Some Code****************/

Thanx

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

It's hard to guess ...

Anyway, you upload ZIP files (which are extracted and the content is indexed then by the repository), plus the asset update workflow is running. That can take a while and consume quite some CPU, but should be async. The whole process of copying the assets itself should not take long.

Jörg

12 replies

rohitm58172886
Level 2
July 9, 2019

Hi, Joerg hoh

               "its getting slow" means when i copy above files under different parent node its taking time nearly 30 sec.As per our assumption it should take max 4-5 sec.When these files under in copy process java reach 90% cpu and again its come back to normal i.e. 3-6%.This happens six times because count of above files are six.

My machine configuration as below

     Ram-12gb

     system type-64 bit

      AEM -AEM 6.4

   

Thanx,

Rohit Mhetre

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
July 9, 2019

It's hard to guess ...

Anyway, you upload ZIP files (which are extracted and the content is indexed then by the repository), plus the asset update workflow is running. That can take a while and consume quite some CPU, but should be async. The whole process of copying the assets itself should not take long.

Jörg