Skip to main content
Question

Dataset Fanout in 2025.2

  • March 17, 2026
  • 3 replies
  • 57 views

edmund.har
Contributor
Forum|alt.badge.img+3

Hi all,

I am experiencing an issue with dataset fanout in my workbench after upgrading to 2025.2.0.0 with Build 25810 (WIN64). The workbench worked perfectly in 2024.2.

The workbench reads in a FGDB file 30,000,000 features using a reader, then performs spatial filtering with coordinate grid tiles and fanout into geopackage files according to the tile names using a writer. The workbench always stopped while outputting the first geopackage file with the following error message.  

Insufficient memory available -- error code was 2 - please read the FME Help section 'Adjusting Memory Resources' for workarounds.

The workbench worked fine when I set the max features to read in the reader as 100,000, but the writer failed once the reader read all 30,000,000 features. I tried lowering the number of features per transaction in the writer but it did not work. 

Is anyone else experiencing a similar memory issue with dataset fanout in 2025.2?

Thank you for your help in advance. 

3 replies

nordpil
Enthusiast
Forum|alt.badge.img+12
  • Enthusiast
  • March 17, 2026

Are there any blocking transformers in the workspace? Just wondering if it needs to hold 30 mill features in memory...


edmund.har
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • March 17, 2026

Hi ​@nordpil I assume the SpatialFilter holds all features before starting dataset fanout to individual geopackage files. 


nordpil
Enthusiast
Forum|alt.badge.img+12
  • Enthusiast
  • March 17, 2026

I don’t think so, but that is easy to test when you run it interactively. But you need to make sure that the filter(s) are loaded before any candidates. I think you could also consider, instead of filtering, reading based on the geometry queries (the tiles) using FeatureReader(s).