AEM slow down when copy node

rohitm58172886

04-07-2019

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

Accepted Solutions (1)

Accepted Solutions (1)

Jörg_Hoh

Employee

09-07-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

Answers (11)

Answers (11)

Jörg_Hoh

Employee

08-07-2019

ok, it seems that you are facing a number of issues....

of course duplicate UUIDs are not allowed; please try a different copy routine which does not copy all properties (as done by the workspace methods), but only the non-protected ones. For example the JcrUtils provided by AEM [1].

Regarding the performance: Depending on the size of the assets and some other (more infrastructure constraints) this copy action can move gigabytes... Can you tell us a bit about your setup and the size of the assets you want to copy?

[1] JcrUtil ("The Adobe AEM Quickstart and Web Application.")

yanirac19051392

Employee

04-07-2019

Move/copy can be an expensive operation.  You should take threaddumps [1] to see what's taking so long and perhaps enable debug logging for query [2] to see if anything can be done.

[1] Take thread dumps from a JVM

[2] Oak Queries and Indexing

rohitm58172886

08-07-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

    cpu_use.PNG

Thanx,

Rohit Mhetre

Jörg_Hoh

Employee

08-07-2019

ok, the size of the assets is not a problem.

Next thing: What do you mean by "is getting slow"? For how long is your AEM slow? Seconds, minutes or hours? Does it require a restart to recover?

Note: When new assets show up in the repository (and copying is a reason for it), the asset update workflow is starting which can be quite resourcen intensive, but which should only take seconds for the assets of the size you posted.

Jörg

rohitm58172886

07-07-2019

Jcr.Utila.copy doing recursively so its try to copy [jcr:uuid] and because of same uuid aem throws below exception

OakConstraint0030: Uniqueness constraint violated property [jcr:uuid] having value

akashk22786878

Employee

04-07-2019

Hi Rohit,

If it is really slow for some basic operations then feel free to raise a support ticket here: https://daycare.day.com/home/createaticket.html

with clear detailed use case to replicate the slowness and thread dumps if specific to your environment.

Arun_Patidar

MVP

04-07-2019

you can try different approach:

adminSession = repository.loginService("readService", null);

Node node = adminSession.getNode("/apps/nodePath/textfield");

Node parentNode =  adminSession.getNode("/apps/parentNodePath");

JcrUtil.copy(node, parentNode, null);

adminSession.save();

aem63app-repo/CopyNodeServlet.java at master · arunpatidar02/aem63app-repo · GitHub