You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I timed the loading of the component and get less than 300ms. It looks like that component is one of the last to start loading and therefore prints its message very late. However, there is still lots being done, in overlapping threads, including the one listed next in the code, which is the processorsPrimer. That runs a sentence through processors so that its lazy values and companion objects get initialized and takes about 1000 times longer. I suspect that is what is taking up so much time and is perhaps being attributed to the other component. This shouldn't have anything to do with a fresh build, like after sbt clean. Maybe a fresh run?
On Tue, Jun 8, 2021 at 9:20 AM Keith Alcock ***@***.***> wrote:
*External Email*
I timed the loading of the component and get less than 300ms. It looks
like that component is one of the last to start loading and therefore
prints its message very late. However, there is still lots being done, in
overlapping threads, including the one listed next in the code, which is
the processorsPrimer. That runs a sentence through processors so that its
lazy values and companion objects get initialized and takes about 1000
times longer. I suspect that is what is taking up so much time and is
perhaps being attributed to the other component. This shouldn't have
anything to do with a fresh build, like after sbt clean. Maybe a fresh
run?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Hey all -- this takes forever on a fresh build:
Do we really need this dep still? AFAIK it wasn't shown to be super useful? Or am I mistaken?
The text was updated successfully, but these errors were encountered: