Hi, we have segmented the workflow into two smaller pieces already, but the size of the one is still getting grow... It is state machine workflow and for this case I'm not sure if it is good idea to break machine states into another workflows.
Anyway, we are experiencing problems with publishing and with first runnig the workflows also. As the IIS pool is restarted every night, every new day the first run of the workflow is really slow.
We are considering to schedule a workflow to run on a blind item at a scheduled time every night, to cache the workflow.