Open dckc opened 3 years ago
my client log is in https://github.com/Agoric/testnet-notes/issues/29#issuecomment-904811805
This was noted as a Phase 1 priority in today's community call.
@mhofman would you please surface the wallet install time in the daily perf stuff? That seems like the next step on this issue. (Feel free to split out that part as a separate issue if you like).
I see it on the testnet retrospective under "next steps".
p.s. Another next step that @dtribble suggested is to look at the wallet code to see why it takes 32 round trips. @rowgraus I leave it to you to nominate somebody for that part.
@michaelfig the sequence diagram we discussed is in...
onBind
look like they could go in parallelE(zoe).startInstance()
could take an ERef<Instance>
(see also: #3837)The loadgen now captures the wallet deployment time and is one of the metric included in the spreadsheet based stats. We actually noticed a regression recently thanks to it.
We could still look at opportunities to pipeline the wallet more, but that should be less pressing once we have #3995. Removing myself and assigning @michaelfig
Currently takes about 5 minutes to fully deploy. Closing this as it should be covered by loadgen work.
Adding technical-debt as I pay significant interest on it most days.
It is sometimes better to just close the fixed issue ...
perhaps. In my estimation, not this time.
Description
I provisioned a testnet client as usual using docker and the testnet faucet.
https://testnet.explorer.agoric.net/account/agoric13lk0cnmehvfqtpcynwq7hx6qu86qtw3cu00qxe
Getting the wallet fully deployed took 22 minutes:
Expected behavior
Didn't this used to take more like 5 minutes?
p.s. The 22 minutes have gone and we're back to around 5 minutes, but we still take 25 round trips to the chain and back. Is that acceptable?
Desktop
cc @warner @michaelfig @rowgraus @katelynsills