HFT: Linux vs Windows
- Thread starter GreenMan
- Start date
Short answer : no. ;-)
The time needed (and skill) to write efficient, multithreaded, latency critical C++, debug it and make it reliable is just prohibitive.
Linux itself gives no guarantees to be more performing than windows, and even if it could be, again, the amount of skill and energy to make it so (and maintain it so) will also be non trivial.
In my experience, the success of such a software will be more dependant on the skill of the people involved, the nature of the algo itself (and the skill of the people designing the algo) and also the time to market for any evolutions (which will be numerous and frequent).
The time needed (and skill) to write efficient, multithreaded, latency critical C++, debug it and make it reliable is just prohibitive.
Linux itself gives no guarantees to be more performing than windows, and even if it could be, again, the amount of skill and energy to make it so (and maintain it so) will also be non trivial.
In my experience, the success of such a software will be more dependant on the skill of the people involved, the nature of the algo itself (and the skill of the people designing the algo) and also the time to market for any evolutions (which will be numerous and frequent).
short answer: yes. ;-)
google linux rtos extensions and network stack configurability and you'll have your answer.
google linux rtos extensions and network stack configurability and you'll have your answer.
Doesn't Linux have about 1% of the market... rebels and geeks? How could it be significant in the landscape of things?
Even if it's the "greatest thing since sliced bread", how important is it going to be to the general population of computer users?
Even if it's the "greatest thing since sliced bread", how important is it going to be to the general population of computer users?
The general population of computer users is not interested in taking advantage of millisecond matters, for real time algos or anything else.
Reasons will differ, but I think that the majority of practitioners in the "every millisecond matters" arena are using Linux for the systems that handle their trading.
It is on a case by case basis.
new() in C# is faster than new() in C++ for example.
Generally speaking, you need to benchmark your particular scenario.
I wouldn't be surprised if C# were on some cases 30% slower than C++. but when you benchmark it, you will see that you spend about 300% more time developing the same (simple) algo in C++ than in C#.
C# is also easier to profile and debug performance related issues for example.
One big drawback of C# for millisecond-dependant algos is the Garbage Collection. There are ways around that though, like ObjectPools.
new() in C# is faster than new() in C++ for example.
Generally speaking, you need to benchmark your particular scenario.
I wouldn't be surprised if C# were on some cases 30% slower than C++. but when you benchmark it, you will see that you spend about 300% more time developing the same (simple) algo in C++ than in C#.
C# is also easier to profile and debug performance related issues for example.
One big drawback of C# for millisecond-dependant algos is the Garbage Collection. There are ways around that though, like ObjectPools.