Skip to main content
Question

How to stop high CPU usage overheads with windows security scanning each FME desktop temporary file write

  • 15 July 2022
  • 1 reply
  • 54 views

ridleyj
Contributor
Forum|alt.badge.img+3

Using FME(R) 2021.2.5.0 (20220331 - Build 21816 - WIN64)  desktop on windows PRO build 2009.1766 65g RAM, 6 cores, experiences massive CPU drain when running a LIDAR density analysis out to raster via the custom transformer as in article - Calculating Point Cloud Density (safe.com)

The two step tiler seems to trigger a Windows security scan when using the FME_TEMP directory as FME writes the (many) temporary cache ffs files down to disk when demanding a 1m high res raster result. The security kicks in and the CPU starts skipping up to 80%+ which drags the performance way down on large LIDAR file sets. Setting the raster res lower (10m) doesn't seem to trigger the same issue

 

The FME_TEMP directory cannot be included in the security white list (corporate policy settings only - as each workstation /individual may have a different FME_TEMP location), and therefore although FME and the install directories are white-listed per FME Community (safe.com), the FME_TEMP directory is subject to security processes.

 

Has anyone else come across this? Is there a workaround? Any advice on whitelisting file type ".ffs " as an option to avoid security scans?

1 reply

redgeographics
Celebrity
Forum|alt.badge.img+45

One easy fix would be to point the FME_TEMP to a folder that's inside the FME install directory (although I'm not sure whether that would be wise from a performance point of view). Alternatively, trying to convince your IT department to white-list the FME_TEMP directory is an option too. Maybe escalate it and point out that this is seriously impeding your performance and/or is preventing you from delivering the results you're expected to deliver.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings