Normally when I unload a workflow, I want to persist it, but I think I want to be able to unload one without persisting. Is it possible?
My main reason for doing this is for performance reasons. I'm currently testing about 130 running workflows. My application starts and loads all these in. They do some execution that doesn't happen to change any state, but does unload the workflow so that
another runtime can pick it up later. With a method profiler, I found that this is one of my bottlenecks, I would guess due to lots of data being persisted.
I do have an idea for a bit of a hack. I could keep a list of instance guids that are "not available for persisting" and then override SaveWorkflowInstanceState in SqlWorkflowPersistenceService to ignore anything in that list. I think that would
accomplish removing the workflow from the runtime, but not actually saving it. I was hoping for a slightly cleaner method though.
View Complete Post