Hi,
We have recently started working on the high level design of a new trading platform that is going to process 100s transactions per second.
As a part of the design we are intending to develop a client desktop application that is going to make use of a number of windows services to process data entered by traders. The services will obviously work as multi threaded applications.
From experience I know of the issues associated with multi threading such as deadlock, race conditions etc.... but do not have much familiarity with dealing with solutions that cater for 100s transactions per second.
Could somebody indicate what additional issues we should consider when so many transactions are being processed?
Thanks
Loading
Mahesh ChandPosted Oct 30, 2010, 6:19 PM
Microsoft's Visual Studio 2010 & .NET Framework 4 provided a way to achieve this by using the Parallel Library and Parallel LINQ in it.
This tutorial gives the idea of Parallel Extension being built by Microsoft to many of its existing features.
The Threads makes us able to run multitasks at a time. In fact Computers (John von Neumann Architecture) don't execute the tasks parallel .The OS gives threads permission (depend on thread priority) to work on CPU. The sufficient degree of parallelism keeps the CPU busy and it is efficient.
This article gives you an idea how to utilize Parallel Extension to Linq or PLINQ.