Command line import utility takes a very long time to load
The client is launching the command line import utility from a Ukraine Server in order to install files into a server in Russia. When launching to utility it takes an extremely long time to load the bootstrap. They want to know if there is a way to limit what gets loaded during the bootstap process in order to spped up the loading of the servlet. They only want to start up what is truly needed to perform the import.
***13/10/2016: Updated by moderator: Lochan to update post with original body text that was lost due to a PDN bug; Apologies for the inconvenience caused***
Accepted Solution
Pegasystems Inc.
US
Doing an import is very database intensive so having the node you are running prpcUtils from be so far from the database server is going to take time. Ideally you want them both to be in the same data center. You can specify your own prconfig.xml and prbootstrap.properties file instead of having prpcUtils auto generate one everytime and thus create a new PegaTemp directory for each run.
# Use the following properties If you want to use a
# custom prconfig.xml or prbootstrap.properties file
#pegarules.config=
#prbootstrap.config=
Pegasystems Inc.
US
The problem is that prpcUtils downloads lots of jars/classes everytime it starts. It take 5-7 minutes when we are running on a server near the database. When the database is not close, it can take hours to load and is not usable. Is there a way to prevent the jar downloads and resuse from a previous launch? Any suggestions would be helpful.
Pegasystems Inc.
IN
Hello ,
From the post i understood that you want to import some archive into your russia server but you have those archives present in Ukraine server .
Is it possible to launch the command line from the server resides in Russia and have the archive locally to avoid the network latency .
can you please provide us the logs to check what are classes which are taking more time to load?.
Thanks,
Arun
Pegasystems Inc.
US
They want to avoid having to run the utility from the server in Russia (they have servers in other countries as well). I assumed it was related to network latency or something loading the jars across the wire. Once the utility is loaded the import happens pretty quickly. The issue is how long it takes to instantiate the utility. I will request the logs from the client.
Pegasystems Inc.
US
Have you had an opportunity to review the logs? Also the client has provided additional info and another related question:
They experimented by putting some jars in the classpath and that cut the load time by 4 minutes locally (jsr94-1.0.jar, prbootstrap.jar, prbootstrap-api.jar, prdbcp.jar). After that it appeared to be resolving all the rules. Is there a way to write out those results and potentially use those results to speed it up more?
Pegasystems Inc.
IN
Hello!
For some reason the content for the original post disappeared after a Moderator edit and we are unable to add it back. Below is the original question for reference!
The client is launching the command line import utility from a Ukraine Server in order to install files into a server in Russia. When launching to utility it takes an extremely long time to load the bootstrap. They want to know if there is a way to limit what gets loaded during the bootstap process in order to spped up the loading of the servlet. They only want to start up what is truly needed to perform the import.
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
US
Per Client:
- Attached is a log of my test against uatps for the AES jar. I removed the cleanup to keep the temp files it creates.
- Then I ran again with the temp directory hard coded into the prpcUtils.xml rather than a dynamic name for the directory. The resulting log is attached as hard_coded.log
EPAM Systems, Inc.
ES
Hi,
Is the issue fixed? If so, Could you tell me how you have addressed it?
I am facing similar kind of issue when importing a file through command line prompt. It would be helpful. Thanks in advance.
Pegasystems Inc.
IN
Hello ,
Sorry for the late response .
Are you still looking out for any assistance on this post .
Thanks,
Arun
Accepted Solution
Pegasystems Inc.
US
Doing an import is very database intensive so having the node you are running prpcUtils from be so far from the database server is going to take time. Ideally you want them both to be in the same data center. You can specify your own prconfig.xml and prbootstrap.properties file instead of having prpcUtils auto generate one everytime and thus create a new PegaTemp directory for each run.
# Use the following properties If you want to use a
# custom prconfig.xml or prbootstrap.properties file
#pegarules.config=
#prbootstrap.config=