Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sandbox is slow to spin up, and slow to respond to first submit. #1230

Open
nickchapman-da opened this issue May 17, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@nickchapman-da
Copy link
Contributor

commented May 17, 2019

It takes about 1.5s for the initial spin up (until the "listening on port" message is printed). Then, it takes another 1.5s to respond to the first call to the command submission service. (Following submissions are much quicker at around 1/100s). The lag of 1.5s for the first submit is not reduced even if we pause for a few second between spinup & submit.

These numbers were discovered while writing unit tests for the haskell ledger bindings. To get isolation, it is convenient to spin up a new sandbox for each test.

@bitonic

This comment has been minimized.

Copy link
Contributor

commented May 20, 2019

@nickchapman-da those number are not unexpected: JVM applications are notoriously slow to start (1.5 seconds seems perfectly in line with the sad status quo), and packages are loaded lazily, which means that we'll compile the relevant package when the first message arrives.

We can improve on the second number by eagerly loading packages, but improving on the first will be tough.

bitonic added a commit that referenced this issue May 20, 2019

bitonic added a commit that referenced this issue May 20, 2019

bitonic added a commit that referenced this issue May 21, 2019

bitonic added a commit that referenced this issue May 21, 2019

bitonic added a commit that referenced this issue May 21, 2019

bitonic added a commit that referenced this issue May 21, 2019

bitonic added a commit that referenced this issue May 21, 2019

mergify bot added a commit that referenced this issue May 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.