Skip to main content
Question

FME works extremely slow

  • September 16, 2015
  • 4 replies
  • 57 views
A

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.

    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    4 replies

    J
    Forum|alt.badge.img+5
    • julien
    • December 2, 2015

    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
    redgeographics
    Celebrity
    Forum|alt.badge.img+62

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

    FME rocks! \m/
    fmelizard
    Safer
    Forum|alt.badge.img+21
    • fmelizardSafer
    • Safer
    • December 2, 2015

    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.

    gio
    Contributor
    Forum|alt.badge.img+15
    • gioContributor
    • Contributor
    • December 2, 2015

    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?

    Community Stats

    32,207
    Posts
    122,305
    Replies
    39,891
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.