-
Notifications
You must be signed in to change notification settings - Fork 14
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
Coping with slow workflow analysis #155
Comments
I don't know much about this part - you may need to talk with Jon. On Thu, Aug 15, 2013 at 10:54 PM, nschneid [email protected] wrote:
When a place gets crowded enough to require ID's, social collapse is not |
...and then it takes several minutes before displaying:
...then it sits for awhile longer until it finds the two realizations that have been invalidated. Then a couple more minutes to check the packages and the work plan (17 task realizations).
In total, on the order of 10 minutes.
It shouldn't be a memory issue because I set the JVM flag to allow 2g and it's only using 1–1.5g.
I have been using fairly restrictive plans to try to limit the possibilities it has to search. But this has not entirely avoided slowness. This plan is only asking for 49 vertices, which should not be too onerous.
Could all the old versions be the cause? Why should ducttape need to examine all the older versions to run a workflow—why doesn't the previous version suffice? If I want to start experiments from scratch, can I safely clear (or rename) the .versions directory as a workaround, or will that cause problems?
The text was updated successfully, but these errors were encountered: