Just to be sure, is FeatureCaching on or off?
Where is the non geometry sensor data coming from and how big is it? Perhaps there is an option to use a databasejoiner to avoid having to read all the data in?
ebygomm wrote:
Where is the non geometry sensor data coming from and how big is it? Perhaps there is an option to use a databasejoiner to avoid having to read all the data in?
It's only about 15k records. I pushed it from SQL Server into MS Access. I had another process doing that for multiple sensors. It is running, just not at the speed I would assume it should. It is joining one polygon and making 15k polygons, so I change it to a temporal layer. I have tested the process, and the result works, but it is just a dog on a system with 64Gb of RAM. FME shouldn't even blink at this process. I also upgraded the FeatureMerger transformer to the latest version, but it didn't help the situation.
Are you using suppliers first?
jdh wrote:
Are you using suppliers first?
No. I could get it to work, but I had to break the processing into separate workbench files, or I should say a fresh workbench file. It was very odd. Either the data was corrupted, or the workbench file, I think. Adding more time based filtering at some point soon. I will have to walk a little slower in my testing.
wisegis wrote:
It's only about 15k records. I pushed it from SQL Server into MS Access. I had another process doing that for multiple sensors. It is running, just not at the speed I would assume it should. It is joining one polygon and making 15k polygons, so I change it to a temporal layer. I have tested the process, and the result works, but it is just a dog on a system with 64Gb of RAM. FME shouldn't even blink at this process. I also upgraded the FeatureMerger transformer to the latest version, but it didn't help the situation.
Out of curiousity, what version of FME are you using?