I’ve recently downloaded an evaluation copy of Aspose Tasks and I’m presently running a set of performance and functionality tests in comparison to the Microsoft Project Object Model API. I’ll label these as the Aspose & MSP application versions for the sake of future brevity.
The code platform is C# (VS 2015) using the Aspose Tasks 2017 version 126.96.36.199. The application frameworks for the Aspose & MSP versions are identical with object property retrieval differences appropriate for the relevant Aspose or MSP API. In each case the application reads the same 83 projects of varying task count and writes the project & task data to a SQLite database, records are written transactionaly for optimum performance.
All Task values are retrieved using the Aspose API Task.Get(Tsk.) method and the following columns are written:
First strike performance test results in Mins: Seconds -
This was a little surprising, I expected a larger performance gain using the Aspose library. Further investigation has identified the WBS value as a performance bottleneck, removing the WBS field from the test reduces the Aspose benchmark to 36 seconds, re-adding WBS increases the benchmark by 2 minutes.
Any idea why the WBS field incurs such significant performance degradation ?