Question

从控制台输出中可以看到：

BEGIN ETL PROCESSOR
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 1055ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 2055ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 3389ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 4389ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 5389ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 6389ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 7488ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 8488ms [0 warnings, 0 errors]
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertic
es/sec) Total time: 9658ms [0 warnings, 0 errors]
+ extracted 236 records (234 records/sec) - 236 records -> loaded 235 vertices (
233 vertices/sec) Total time: 10663ms [0 warnings, 0 errors]

你可以在我的ETL配置： https://groups.google.com/forum/#!topic/orient-database/JbMrhqSGXGM

那么在最初的10秒内，它似乎无所事事。

仅供参考：在MySQL表中有大约250.00个条目，只有colums从那里获取

Answer 1

它与您访问数据库的方式有关。可以有本地和远程等等。您应该测试哪一个最适合本地大量导入。

OrientDB - 为什么ETL在开始加载之前需要一些时间

1 个答案: