span8
span4
span8
span4
嗨,
I have problem with FME 2018 where my workspace processing just stalls at one particular NeighborFinder transformer.The workspace has several NF transformers with fairly similar parameters, but only one is causing problems.It processes either one or none of the features after which nothing more happens, the processing just stalls.
I don't get any errors, FME doesn't crash, the last line in the log is加工基地功能(S)...and even though the transformer should process the data in a couple of minutes, nothing happens even if I leave it running overnight.
However the workspace runs just fine on both FME 2018 and 2018.1 (32 bit) if I reduce the processing area, but even running the workspace at full processing extent, I don't seem to have any memory issues.Furthermore, I have tried to run the same workspace on FME 2017.1 and 2019 beta (32 bit) and there I have no issues whatsoever.Is it perhaps a bug of sorts in FME 2018?
The overview of the workspace in question:
需要明确的是,这是一个32位仅与FME 2018的问题?如果是这样的话,我强烈怀疑它必须做的问题与我们的高数据量/低内存处理,我们必须在某些情况下(而且似乎你幸运地是在选择和
是的,它与32位FME 2018和内存处理看起来可能是这个问题的根源问题的问题。不幸的是我不能共享数据,因为这些数据库的内容是不公开的访问呢。
如果有帮助,然后从FeatureReaders A,B,C来多边形数据,以及从F线的特征。此外,ADS书签NeighborFinder接收略高于810 000候选,并且超过56 000基地特征;AY得到4 700候选和大约750碱基特征;KU1越过710 000候选,并且约16 500个碱基的特征和问题FeatureReader接收约17 500的候选和16层500个碱基的特性。
我想我能找到解决这个问题,如果我FeatureReaders引发反复折腾一点,所以,所有的数据将不会同时读取和一些NeighborFinders将完成他们的工作,别人得到他们的输入数据之前。
谢谢回复!
不幸的是你的屏幕截图显示不出来,所以很难,看看是否有您可以对工作流程进行任何更改,使其更少的内存密集型。亚搏在线
有一点要考虑,如果你有硬件,是尝试FME的64位版本。另外...你提到的2019测试没有问题,那正式发布是由于推出...
嗨,
I'm also facing the same issue...
加工基地功能(S)...is shown in log file.
I thought, it is memory issue and left for 12+ hours but no change.
@hlh, Is there any solution identified?
Pratap
我认为这将有助于如果你可以将其添加为新的问题(与基准回到这个)。它甚至可能不是相同的问题在这里或那里可能现在不同的信息,这可能有助于。如果您可以提供日志文件和工作区,将极大地帮助在未来的一个解决方案。
You need to create your own partitioning if you cannot use groupby.It will be worth the effort.
Do this by adding a code that does enable you to split up the data into groups.I do this when I use NeighborFinder on a national dataset of address points and roads.In my case one layer (roads) has a district code but the addresses do not.So I do an overlay first to add a district code.
Actually there are so many operations I create a workspace runner that runs the workbench repeatedly for each district by having an SQL filter that selects just the features for each district.Each process then runs on a small set very quickly so the overall time is not only much reduced, but it never fails due to memory overloads.
Don't have a suitable polygon layer?Then invent one.You could just make a grid, or a binary tree grid where the counts are more equal.
If you have an option to use a Group By, the NeighborFinder performance increases by a lot (usually).
Still strange that in other versions this issue does not occur.
As you have run the workspace in FME 2017.1, I assume it is built using an older version.
Can the NeighborFinder transformer be upgraded (newer version of the transformer)?
希望这可以帮助。
© 2019 Safe Software Inc |Legal