slow key access / generation - scrypt?

[dckc]

on this branch I'm working on, something takes 5-10 seconds at start-up and on key generation.

The branch involves switching from tweetnacl to various things including scrypt; I blew by some performance warnings in the scrypt.js docs; better start looking there.

[dckc]

I found the scrypt issue: the cost parameter (n) was unusually large (c9502f9e3caa).

But loading is still slow (and compute intensive). I'm not sure why.

[dckc]

git bisect shows the problem started in

• d5cdc94ea3d0 Jun 5 fix: use secp256k1 rather than ed25519 (WIP)

the size ballooned:

asset ethProvider.js 1.61 MiB [emitted] (name: ethProvider) 1 related asset
asset popup.js 1.32 MiB [emitted] (name: popup) 1 related asset
asset options.js 1.31 MiB [emitted] (name: options) 1 related asset
asset pageRelay.js 7.92 KiB [compared for emit] (name: pageRelay) 1 related asset

up from

asset ethProvider.js 81.1 KiB [emitted] (name: ethProvider) 1 related asset
asset popup.js 80.9 KiB [emitted] (name: popup) 1 related asset
asset options.js 75.2 KiB [emitted] (name: options) 1 related asset
asset pageRelay.js 7.92 KiB [compared for emit] (name: pageRelay) 1 related asset