Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Components
Assignee
Attila VamosAttila VamosReporter
Attila VamosAttila VamosPriority
MajorFix versions
Affects versions
Details
Details
Components
Assignee
Attila Vamos
Attila VamosReporter
Attila Vamos
Attila VamosPriority
MajorFix versions
Affects versions
Created February 13, 2015 at 9:32 AM
Updated February 17, 2015 at 4:29 PM
Resolved February 17, 2015 at 4:29 PM
To help digital forensic to discover what really happening behind the ECL/ECL Watch scenes the DFU server should provide information (entries in server log) about which kind of splitter/partitioner (CSV, quick csv, XML, etc.) used in file spray.
This extra information could help to solve cases like this:
"I have also run the job through ECL Watch and through code. Both are spraying exact same 12GB file (input.csv). One job was run using the ECL Watch and the other one using the code. Through ECL Watch: DFU WU ID: D20150210-131724 Logical File Name: through::eclwatch::input.csv Total time taken 3m 29s, Average transfer 58907KB/sec Through Code: ECL WU ID: W20150210-132115 DFU WU ID: D20150210-132115 Logical File Name : through::code::input.csv Total time taken 6m 58s, Average transfer 55123KB/sec It took exactly double the time. As if it's doing two passes of the file. The job just waits for a long time before it starts. Once it starts, the speed is pretty close, I guess"