Would love an easy way to show processing time PER transformer to quickly identify transformers that a performance bottle necks.
The number would be the processing time of features being processed by that transformer.
Either by a report, log or visually on the workbench when running in the feature caching mode.
This would be of great help to prioritize work on performance/workbench timings to schedule data processes on time.
+59I do have an enhancement request already filed with the developers to do something like this. In my case it was to highlight each transformer as it is processed, but this is very similar. The reference number is FMEENGINE-47325
However... it should be noted that FME doesn't process data one transformer at a time. It processes data one feature at a time. Therefore it's hard to calculate exactly how much time is spent on one particular transformer, or which transformer is currently being processed. That's just to emphasize that this isn't a simple task to achieve, and that if we did implement this, it might cause a slowdown in processing. I would still like to see something like this, but I wouldn't expect it any time soon!
+22There was an FME World Tour talk showing how to open the developer back door on this: https://www.safe.com/presentation/fme-performance-profiling/ -- Results can be hard to understand but this is the foundation upon which we'd built a nice UI one day.
If I noticed a poor performing workbench one day then I could take it off into debug mode to figure out what's going on.
See also the suggestions FMEENGINE-60629 and FMEENGINE-60631 that I submitted at the 2019 Partner Summit, there's a bit of overlap with some ideas here.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
