Skip to main content
Solved

Any other tested FME2022 (FME(R) 2022.0.0.0 (20220428 - Build 22337 - WIN64) and experience slow Esri Filegeodatabase Reader is slower than "used to be"

  • May 9, 2022
  • 5 replies
  • 36 views
palhermans
Contributor
Forum|alt.badge.img+10

A very simple workspace using ArcObjects Esri FileGeodatabaseReader and output to an Inspector. Duration 16.5 seconds with FME2022 and similar workspace duration is 10.5 seconds with FME2021.2

 

Logfiles attached and a Excel spreadsheet with output from FME_PROFILE_RESULT_CSV

 

best

Pål Herman

Best answer by kailinatsafe

Hi @kailinatsafe​  and thanks for reaching out. I am not allowed to share the data public but have simulated something similar with a workspace:

  • 20000 points "randomly" generated within a X and Y range - written as points to the filegeodatabase
  • Buffered these points "randomly" with buffers in range 5 to 50 meters , replaced with a 2D box which is rotated "randomly" within -45-45 deg and written as polygons to the geodatabase
  • chopped the boxes to max 2 vertices and written results as lines

All to simulate building centerpoints, outlines and polygons. With these data FME2022 is about 30% slower (using the GUI). With the actual data we are at approx 40%.

Best Pål Herman (zipped geodatabase attached)

 

 

Hello @Pål Herman Sund​ , thanks for sharing your data. I was able to reproduce the delay you're describing between 2021 and 2022.0. There are a few things that appear in the 2022.0 logfile, that are not logged in 2021 - so it seems like something has slightly changed here. This has been filed as FMEENGINE-73370. I've added a note to have this thread updated once resolved as well. Best, Kailin.

pH
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.

5 replies

palhermans
Contributor
Forum|alt.badge.img+10
  • palhermansContributor
  • Author
  • Contributor
  • 46 replies
  • May 9, 2022

..workspaces are both made in their respective FME versions - so no issues with not updated readers

pH
kailinatsafe
Safer
Forum|alt.badge.img+23
  • kailinatsafeSafer
  • Safer
  • 720 replies
  • May 9, 2022

..workspaces are both made in their respective FME versions - so no issues with not updated readers

Hello @Pål Herman Sund​ , would you be able to share a copy of your FGDB? If you're unable to share it on the FME Community, please submit a support case with us so we can take a closer look! Best, Kailin.

palhermans
Contributor
Forum|alt.badge.img+10
  • palhermansContributor
  • Author
  • Contributor
  • 46 replies
  • May 10, 2022

Hi @kailinatsafe​  and thanks for reaching out. I am not allowed to share the data public but have simulated something similar with a workspace:

  • 20000 points "randomly" generated within a X and Y range - written as points to the filegeodatabase
  • Buffered these points "randomly" with buffers in range 5 to 50 meters , replaced with a 2D box which is rotated "randomly" within -45-45 deg and written as polygons to the geodatabase
  • chopped the boxes to max 2 vertices and written results as lines

All to simulate building centerpoints, outlines and polygons. With these data FME2022 is about 30% slower (using the GUI). With the actual data we are at approx 40%.

Best Pål Herman (zipped geodatabase attached)

 

 

pH
kailinatsafe
Safer
Forum|alt.badge.img+23
  • kailinatsafeSafer
  • Safer
  • 720 replies
  • Best Answer
  • May 10, 2022

Hi @kailinatsafe​  and thanks for reaching out. I am not allowed to share the data public but have simulated something similar with a workspace:

  • 20000 points "randomly" generated within a X and Y range - written as points to the filegeodatabase
  • Buffered these points "randomly" with buffers in range 5 to 50 meters , replaced with a 2D box which is rotated "randomly" within -45-45 deg and written as polygons to the geodatabase
  • chopped the boxes to max 2 vertices and written results as lines

All to simulate building centerpoints, outlines and polygons. With these data FME2022 is about 30% slower (using the GUI). With the actual data we are at approx 40%.

Best Pål Herman (zipped geodatabase attached)

 

 

Hello @Pål Herman Sund​ , thanks for sharing your data. I was able to reproduce the delay you're describing between 2021 and 2022.0. There are a few things that appear in the 2022.0 logfile, that are not logged in 2021 - so it seems like something has slightly changed here. This has been filed as FMEENGINE-73370. I've added a note to have this thread updated once resolved as well. Best, Kailin.

palhermans
Contributor
Forum|alt.badge.img+10
  • palhermansContributor
  • Author
  • Contributor
  • 46 replies
  • May 11, 2022

Hello @Pål Herman Sund​ , thanks for sharing your data. I was able to reproduce the delay you're describing between 2021 and 2022.0. There are a few things that appear in the 2022.0 logfile, that are not logged in 2021 - so it seems like something has slightly changed here. This has been filed as FMEENGINE-73370. I've added a note to have this thread updated once resolved as well. Best, Kailin.

Thanks @kailinatsafe​

pH

pH

Community Stats

32,066
Posts
121,745
Replies
39,692
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.