I have a long running dll written in Fortran (un-managed code and not COM
compliant) that I am calling from UI in VB dotNet.
I originally called it from the UI thread but it was tying up the interface
while in execution. My example was taking 20 seconds to complete.
I changed the call using System.Threadin g.ThreadPool.Qu eueUserWorkItem and
it fixed the UI problem but now takes 200 seconds to complete!
I did not expect this kind of performance hit here.
I created a COM dll in VB6 that runs for 20 seconds (just a loop to test the
behavior) and changing between the
System.Threadin g.ThreadPool.Qu eueUserWorkItem and a regular call has no
effect on the processing time.
Is the performance hit to the fortran dll caused by it being a non- COM
compliant dll?
TIA
compliant) that I am calling from UI in VB dotNet.
I originally called it from the UI thread but it was tying up the interface
while in execution. My example was taking 20 seconds to complete.
I changed the call using System.Threadin g.ThreadPool.Qu eueUserWorkItem and
it fixed the UI problem but now takes 200 seconds to complete!
I did not expect this kind of performance hit here.
I created a COM dll in VB6 that runs for 20 seconds (just a loop to test the
behavior) and changing between the
System.Threadin g.ThreadPool.Qu eueUserWorkItem and a regular call has no
effect on the processing time.
Is the performance hit to the fortran dll caused by it being a non- COM
compliant dll?
TIA