On 2/2/12 10:37 AM, Tankred Hase wrote: > > > > I switched the way this string grew to be more optimized, and it > seems to run quite a bit faster on my machine now. Please try out > the new code and let me know if you see improvements > > Again: fantastic! > > > I retested and although Chrome suggests that the tab has crashed, if I > wait a bit, it encrypts/decrypts successfully now. Great, Thank you! > > Maybe it would make sense for me to put the encryption logic in > a separate web-worker thread, so that it doesn't block the UI. I > attached a screenshot of the chrome profiler if it helps.
That's a cool approach, it would be very cool if the "cpu-intensive" process would also be able to estimate the "amount of time required to complete it's job" and provide a "progress-update" to the UI-process so that it would be possible to show a "progress-bar" for the operation. > > I will probably do some more benchmarking for openpgp.js in the form of > more qunit tests as soon as I get to it. But thanks for your support > everyone so far! I love you :* -naif _______________________________________________ http://openpgpjs.org
