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.
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 .
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?
"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.
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.