Question

Is it possible to save temp to DFS when declaring environment variable for FME_Temp?

  • 23 September 2021
  • 2 replies
  • 1 view

Is it possible to save temp to DFS when declaring environment variable for FME_Temp? We currently would like to seperate the temp data that gets created when running a work space to hit DFS, which resides on premium SSDs, as well as benefiting from deduplication. Is it possible to do this via DFS going across the network, it sees the location specified within the user environment variable pointing to it's respective location on DFS. It also creates the folders on DFS, however it still writes to the C volume of the session host being ran on going to C:\\users\\users\\username\\appdata\\roaming\\safe software\\fme. Or is this only possible if I added an additional hard drive to our virtual machine, then brought online and provisioned, and changed user environment variable for fme temp to point there? I'm new to the application, and if anyone is able to assist, it would be vastly appreciated. Thanks!


2 replies

Userlevel 4

I don't know what kind of throughput you are able to get to/from your DFS, but generally speaking it's not recommended to point FME_TEMP to anything remote. When running translations on larger datasets or when feature caching is activated, quite a lot of temporary data files will be created and these will be specific to each process, so I'm not sure how much deduplication you'd benefit from. The speed of read/write operations to FME_TEMP will potentially have a big impact on translation speed in FME, and most networks are orders of magnitude slower than a local hard drive, even if it's not an SSD.

 

I don't know what kind of throughput you are able to get to/from your DFS, but generally speaking it's not recommended to point FME_TEMP to anything remote. When running translations on larger datasets or when feature caching is activated, quite a lot of temporary data files will be created and these will be specific to each process, so I'm not sure how much deduplication you'd benefit from. The speed of read/write operations to FME_TEMP will potentially have a big impact on translation speed in FME, and most networks are orders of magnitude slower than a local hard drive, even if it's not an SSD.

 

10-4, thanks Dave. I'll go ahead and add an additional HDD to the VM and provision it, then have the temp go there to the native session host which the workspaces are being run on. [TGS Icon Website]<https://www.transgloballlc.com/> Brandon Cohen Cloud Services Manager Office Phone: (817) 529-1180 Direct Line: (682) 291-9440 Mobile: (425) 229-5724 Mailing: PO Box 1001, Forth Worth, TX, 76101 [LinkedIn icon]<https://www.linkedin.com/company/transglobal-services-llc> [Facebook icon] <https://www.facebook.com/Transgloballlc/> [Twitter icon] <https://twitter.com/transglobal_llc?lang=en> [Youtube icon] <https://www.youtube.com/channel/UCyD5V9IYHNR_oMU0LzZS4dQ/videos> CAUTION:This transmission, including any attachments, is for the sole use of the intended recipients and contains information from Transglobal Services LLC that may be privileged and confidential. If you are not the intended recipient, or the person responsible for delivering this information to the intended recipient, please notify the sender immediately and delete the original transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, printing, distribution, or other use of any of the information contained in or attached to this transmission is strictly prohibited.

Reply