Skip to main content

Hi all,

 

 

I run FME workflow an hour ago, made some changes (not serious at all), and when I tried running it again, it reads GML data set extremely slow, really really slow. What could be the reason for this?

I restarted computer serveral times, emptied TEMP directory, diconnected from network, and now I don't know what to do.

How many features do you read ?

Your PC/Server follows these requirements ?

Recommended Requirements
  • Intel®️ Core i7 CPU
  • 8 GB of RAM (16 GB on a 64-bit OS)
  • 50 GB of available hard-disk space
  • A Solid State Drive (SSD) can provide significant
  • performance increases
Minimum Requirements
  • Intel®️ Pentium®️ 4 Processor
  • 4 GB of RAM (8 GB on a 64-bit OS)
  • 20 GB of available hard-disk space

In addition to what Julien asked, what were those changes that you made? Maybe they were serious after all.


How many features do you read ?

Your PC/Server follows these requirements ?

Recommended Requirements
  • Intel®️ Core i7 CPU
  • 8 GB of RAM (16 GB on a 64-bit OS)
  • 50 GB of available hard-disk space
  • A Solid State Drive (SSD) can provide significant
  • performance increases
Minimum Requirements
  • Intel®️ Pentium®️ 4 Processor
  • 4 GB of RAM (8 GB on a 64-bit OS)
  • 20 GB of available hard-disk space

Examine your log file carefully -- and turn on the timing output -- that should give some indication.


Obiously the changes were very influential.

You migth have set some tolerance to tight, for instance. (i.e. Hullaccumulator is famous for that)

Or inadvertently forced a endless search. Or huge spatial comparisons.

Or created or forced fme into a so called "catastrofic regexp". This will slow things down seriuosly.

Show your workbench?


Reply