AVEVA Intouch using single thread or multi thread ?

Hi, View.exe is single core, so yes, you need to take care so that long-executing graphics scripts are not locking your application and you should try to use asynchronous methods when possible.

Darn ! thanks for clarifying !  So pumping more CPU is basically useless then ! Is system platform OMI Multi thread or is that single thread as well !  I'm thinking with AVEVA Launching unlimited single core is a really bad approach !

Also another question, is Intouch web server multi-threaded ? I really hope it is

System Platform includes your Objects and Application Engines.

An Application Engine (aaEngine.exe) is single core, but with several Application Engines you can have multi core solution with load distribution over several engines.

So on a Object server you can utilize more cores, on your OMI Client computer there is no real need for spending extra money on cores, then its better with high CPU Mhz, but of course its worth to have multi core to let Windows balance its other tasks.

Richard Köhlerstrand  do you have any legacy project that i can use for an upgrade ? The default Intouch project is too basic and I'm looking for a bit more real life projects that i can use for demos

rickard.norin  any comments on this please ? Any plans to make it multi-thread for performance ?

Hi,

An InTouch solution may include a fair amount of components and processes such as view.exe, alarm manager, communication drivers, web server, Historian, Reports, etc.

These processes are subject to load balancing by the operating system whcih will utilize mutliple CPU cores when such are available.

View.exe is, however, monolithic and will not distribute across cores. At least not in a simple single-node architecture. For larger applications, say 100k+ tags, we recommend a tag server architecture which splits the tag server from visualization client processes. This can be achieve with either dedicated client nodes or with a single Remote Desktop Services host. In case of RDS hosting, the view.exe sessions for server and clients will be separate processes which the operating system may schedule across multiple cores.

As we progress forward with significant investments in future versions of InTouch, you will see an increased granularity in the software architecture as well as adaptation to parallel processing as opposed to high Hz processing.     

This is the answer I'm looking for !!! Can you explain if this was licensing under Intouch unlimited since it allows for only one App but tag server architecture will require two apps ( one for tags , other for clients ) , I have done using two apps for this above reason and my bracket for this is much lower than yours ( 30k + tags ) , For Intouch i would like to split tag fetching and manipulation services versus visualisation. 

I'm thinking that InTouch Unlimited Professional and Premier editions should be able to accomodate an RDS-based tag server architecture. If it doesn't, I'm open to discuss fixing that

Hi Rickard, web doesn't seem to work in this kind of architecture, I have provided Intouch professional as the solution but a two app solution causes issues within RDS environment. Honestly , the real treat would be to allow multiple applications so that customers can slowly upgrade from legacy to RDS environment. .