01-21-2011 07:57 AM
In addition to the question Christian posted about the size of the dat structures involved, the nauter of teh dll and how it is called can play a factor.
1) The data size, if large can slow things down becasue there are some circumstances where LV will copy the data to be used by the dll.
2) The nature of the dll I mentioned has to do with "is it thread-safe" and is the call node configured to run in a thread other than the UI thread.
Note:
Techincally speaking neither of those really affect the time required for the dll to execute but do influence how quickly we can invoke the dll.
Done splitting hairs,
Ben
01-22-2011 07:20 AM
Bladhart,
Ignore all these guys, they dont know what they are talking about. It will take exactly 7.9882391 seconds everytime
Rgs,
Lucither.
01-22-2011 01:00 PM
Lucither wrote:Ignore all these guys, they dont know what they are talking about. It will take exactly 7.9882391 seconds
You got your units totally wrong. He's asking for a "speed", which contains inverse seconds as part of the unit. You are giving an answer in units of seconds which is thus completely and fundamentally incorrect, irrespective of the value. 😄
So, what kind of "speed" are we looking for? Lines/second? operations/second? crashes/hour? steps/minute? CPU ticks/second? (that last one we can answer from the 2GHz, unless you are on battery :o). 🙂
01-22-2011 01:39 PM
Assuming not overly advanced lines we can assume something like 1 line/clock cycle under optimal circumstances.
/Y