TS4.1 Multicore example?

[j_dodek]

Hi,

according to the feature List of TS4.1 there is multicore support.

Are there a some examples dealing with mutli core support, where

I can see (good) / turn OnOff (better) / selecting (best) threads on the cores. 

or is the feature just a slogan (worst).

Until this is not clarified i will wait to install TS4.1 on my maschine

and later in productionfield.

Greetings

Juergen

[Santiago D]

Juergen,

With NI TestStand 4.1, parallel test features such as the parallel process models, auto-scheduling support multi-core processors by allowing different executions and threads to run on different cores in a processor.  Not all test executives support multi-core processors.  If the test executive is not built using a mutli-threaded architecture or provides tools to create threads, the test executive will be forced to execute on a single processor core. 

If you want to view how threads run in parallel using the parallel process models, take a look at the new resource profile that is highlighted in the What's New in TestStand 4.1 presentation.  Although the resource profiler will let you see how different threads execute, it doesn't display what core each thread is running on.

We appreciate your feedback on increasing the features for multicore support to display which core each thread is running on, and controlling what cores will execute each thread.  We will take them in consideration in future versions.

Santiago D

National Instruments

[j_dodek]

Hi Santiago,

Thank you for pointing me a link to your web-cast/prestentation.
I have watched it.

Very interresting was the resource profiler.
It seems that this could be a very helpful tool
for my daily tasks in progamming and maintaining TS sequnece files.
I think with it I am able to find a lot of "resource" leaks in my
Sequence-Files.

My main-question was answered at the beginning of the cast. You have said
that core distribution is provided by the OS. So i am wondering why this
feature is not supported under TS4.0? Is there another thread initialization
on TS 4.1?

It seems you are the right man for improvent ideas:
I have some points on TS/SwitchExecutive(SE) which i was faced during watching your cast.

1. Switching routes in SE. In your example everything looks clear and simple.
   But if you have a teststation with an adapter interface (for example Virgina Panal)
   this is unsusable. On these maschines you have multi adpater/different Uut support.
   If you configure your routes for juest one UUT on the maschine this SE works well.
   But what do you do if you have more than one UUT on the maschine ?
   - Adding each Uut's routes to the SE-file ! maybe OK if there are 2 differnt uuts
   - Loading a SE file for each material-number ?
       Tell the operator: Go to MAX an load your stuff you need ? bad!
       Better : Use SE-Api while in LoadSequenceFile Callback and load what you need
       automatically. This sounds good and is really working! but also unusable because
       you have to be extremly carefully during programming your Sequence files. Never forget
       to save your new created routes in SE when closing the TS edtior.
       And later you have to manage the SE and TS files !
   Suggestion: TS manage internally a particular SE file.

2. Graphical routing:
   Have you ever connect a route for example on a 4x256 Matrix from
   col_0 to col_255 ?
   Well you have to scroll horizontal! You cannot use the mouse wheel effectiv.
   and not to mention you never see the hole connection on screen!
   Suggestion: Turn rows with colunms so you can use the mouse wheel. Is assume a row length
   of 16 enough in most cases. 
   I did it completely different ! I used a colored plane for this stuff.

3. If you are programming your steps and and want add a new route you have to leave TS and
   switch to MAX/SE.
   OK there is a link button but that is the same !
  

I think this should be enough for the fist time.

Greetings from the Lake of Constance, Germany

Juergen

[Santiago D]

Juergen,

Thank you for the additional feedback on NI Switch Executive integration with NI TestStand.  I forwarded your forum post to the NI Switch Executive team so they are aware of your recommendations.

Your question on whether NI TestStand 4.0 supports multi-core processors is a very good one.  In order to take advantage of all cores in a multi-core processor an application has to be multi-threaded.  NI TestStand 4.0 shares the same multi-threaded architecture as 4.1, so both versions support multi-core processors.  We highlighted NI TestStand's support for multi-core processors in NI TestStand 4.1 because of the recent increase in use and awareness of multi-core processors from our user base.

Santiago D