Package creation takes too long [~25sec] - how to optimize?

This includes the loading of the signing session? Or is this just the createPackage() portion?

It was just the eslClient.createPackage() statement. The call to createSessionToken() was 1sec.

Hi Michael, just a follow-up, I've also tried the sample test project that comes with eSignLive SDK and just swapped-out the test document there with my pdf, and it's also taking that much time (around 23-25 seconds) for just the createPackage() statement to complete.

Okay. I just didn't know if that counted the createPackage and the load time for the signing session to actually be displayed in the portal. Is this against sandbox, production, or both? Unfortunately with performance issues you'll likely have to go through [email protected]. I don't know your process, so I don't know what to suggest as far as breaking it up to see if any of those long waits can be minimized. For example, if the end-user has to do more than just click a button, like fill a form or something, you could create the package first and then add other items later (add signers, documents, etc). If you have this opportunity, it could help break things up. Another thing could be if any documents in the package are static, you could try using a template to see if that reduces any delay times.