FME Desktop 2014 a lot slower..?

Ok, I've timed it.

 

 

Startup takes 1:15 (splash screen shows for 54 seconds)

 

Loading a Blank Workspace (!) takes 21 seconds

 

Shutting down (Blank Workspace, no save) takes 22 seconds

 

 

All this used to be at least 2-3 times faster in FME 2013.

 

 

Does anyone else experience this too?

Curiously, I posted a similar question few minutes ago. To me FME 2014 64bit seems slower than FME 2013 32bit. Have you notice something similar during translations?

@Burton449: I have not experienced a noticeable difference in the time it takes to run translations.

 

I only experience delays when:

 

- Starting/shutting down the application

 

- Opening and closing workbenches

 

- Trying to insert a new transformer by typing its name somewhere in an empty part of the workspace

 

 

Could it be that FME 2014 stores (and loads) more data to and from the roaming user profile than previous versions? ESRI's ArcMap also runs sluggishly on my PC for that exact same reason. Unfortunately, I cannot do much about it, since I cannot move this data to a local folder because of group policy...

Hi Sander,

 

 

We always strive to make FME as speedy as possible, so we take issues like this seriously.  We are currently investigating what may be causing these issues for you.

 

 

Iris

Hi, this may be connected but after I installed FME Desktop 2014 32-bit version (we have the ESRI edition licence), my ArcMap 10.2.1 took 40-60 minutes just to open a blank document (!!!). Also when running Python scripts in ArcMap I was getting random FME licensing error messages. The two applications should be completely stand-alone.

 

 

While the ArcMap splash screen was hanging on my screen, I opened the Windows Task Manager and noticed continual polling of the lmgrd licence manager, which manages both the ESRI and FME floating licences on different servers. The Resource Monitor also showed ArcMap polling the FME libraries in the Associated Handles and Associated Modules windows. At the time our only FME licence was in use by another user.

 

 

After I uninstalled FME, my ArcMap returned to normal. Not sure what is going on here, or whether this is a Safe or ESRI problem, but any ideas would be welcome.

 

 

Dave 

Have you contacted people  from Safe about this issue? If yes, please think to communicate their answers here.

Yes, I contacted them about this. I believe they are working on it, but until know I haven't heard anything specific yet.

In the meantime, I've found out myself that this problem only occurs (at my company) with laptops. Desktops seem unaffected. The laptops have Windows Sync enabled, which constantly synchronizes my My Documents folder (which is a roaming one). This folder is used by FME to read/load transformers and so on. With Process Explorer, I found out that FME2014 also writes to this folder a lot, for some reason. FME2013 only seemed to do a lookup in the registry, which obviously is a lot faster. Unfortunately, I cannot disable Sync (group policy). I did choose "Make Offline" for the My Documents folder, which definitely made FME2014 faster, but I need to do this every time when I start my laptop...

It would be awesome if a user was able to choose the location where FME stores its user data. 

Hi all,

 

We did find one of the issues which was causing the slowdown on the startup of FME 2014. The fix is available in FME 2014 SP2 beta available on the download site at http://www.safe.com/beta. If any of you download it and try it out please contact us at support with your feedback - http://www.safe.com/supportrequest. We are very interested in solving this problem so we need the feedback as it is a hard issue for us to reproduce in our environment.

 

 

Kind regards,

 

Robyn Rennie

 

FME Desktop Support

I've just tried the SP2 beta and the problem seems to be solved! No more delay at startup and shutdown and - even better - no more delays before the quick-add dialog pops up while I type in a transformer name.

Thank you so much for your work! Looking forward to the actual SP2 release :)