On 28/05/2012 16:01, Alan R Williams wrote:
Donal and I were just looking at this. It appears that it is the storing of the provenance information that is slowing down the workflow run. Can you try running it with provenance turned off? It is under Preferences -> Data and Provenance.If that works OK, then the next thing to figure out is why the provenance storage is taking so long.
We checked the differences and found that there was a number of significant configuration changes between the two versions. In particular, Anja's installation of 2.3.0 was configured to use *much* more memory than standard and to keep the intermediate data in memory. The 2.4.0 installation was using stock settings, with provenance capture (but then that was turned in 2.3.0 too) and data written to disk; no wonder it was rather slower...
Initial take-home message? Disks are slower than memory (of course!) and configuration changes are easy to forget.
Donal.
<<attachment: donal_k_fellows.vcf>>
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
