PipelineExecuter = new SingleThreadedPipelineExecuter();
That executor internally uses Caching to speed up other operations
within the pipeline. You can attempt to use the
ThreadPoolPipelineExecutor but you may run into similar issues but
with too many threads holding onto memory at the same time.
I have a very simple non-caching pipeline executor that we use when
working with very large datasets (millions of records.) Try it out. If
it works well we can have it officially added as an option to Rhino
Etl. Here is the code.
public class SimplePipelineExecutor : AbstractPipelineExecuter
{
protected override IEnumerable<Row>
DecorateEnumerableForExecution(IOperation operation, IEnumerable<Row>
enumerator)
{
foreach (Row row in new EventRaisingEnumerator(operation,
enumerator))
{
yield return row;
}
}
}
Nathan
> --
> You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.
> To post to this group, send email to rhino-t...@googlegroups.com.
> To unsubscribe from this group, send email to rhino-tools-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
>
>