从控制台输出可以看到:
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 个条目,仅从中获取列
最佳答案
这与你访问数据库的方式有关。可以有plocal和remote等等。您应该测试它们,看看哪一个最适合本地大规模导入。
关于mysql - OrientDB - 为什么 ETL 在开始加载之前需要一些时间,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/25362505/