Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
MultiCharts and MultiCharts .NET: where are indicators more performant?
Assume one would like to write chart indicators, and have several copies running at once. At some point, performance may bog down. Who can say whether, all else being equal, performance would be better in MultiCharts or MultiCharts .NET? Running multiple instances is an option for both versions.
Can you help answer these questions from other members on NexusFi?
according to the Multicharts developers MC.NET doesn't bring a speed advantage over regular MC, it just brings the flexibility of .NET. Besides that your question is hard to answer as it depends on a lot of factors. For example how good each code is optimized for performance.
If I'd have to take a guess I'd say you either see no difference or a slight benefit from regular MC.
Regards,
ABCTG
The following user says Thank You to ABCTG for this post:
Thats the question I was asking myself when the .Net-Version was introduced. It depends how the functionality is built. Both versions have core functionality in common and presuming that they use one development branch for both versions my question was whether PL is building on the .Net - libraries. In this case this one additionaly architecture layer needing to propagate functionality up to be used by PL is decreasing the performance. During a support live-chat I had no clear answer to this, it rather seemed mixed.
The .Net-Advantage is the ability to use way more resources than ever possible with PowerLanguage. Many things are not or hardly possible to realize within MC but in MC .Net. Hence you'd do complex things in Powerlanguage to archieve the same things easily done with .Net. That can give you a lot of performance advantage.
In the end it depends on the developed indicators, strategies, ... whether the .Net-Version is slightly faster or a little more. So you can outsource code from your PL-Code to your own DLLs which would give good performance.
Imho there are other questions more important to decide between one of them. With .Net bigger projects are way more scalable and flexible, where smaller things or just short tests are done very fast with PL. With .Net you'd have to write 2 or 3 times the code to archieve the same within PL
The following user says Thank You to PK 1 for this post:
* I have not experienced your drop in performance with either MultiCharts or MultiCharts .NET. As ABCTG already notes, performance is dependent on your code and hardware. In other words, poorly written code in MC .NET is much much slower than good code written in MC.
So I would personally not choose a trading platform based on its possible speed, but in part based on how good I think I can program for it. For example, Sierra Chart is presumably quick. But I don't know C++, so it would be slow in my hands.
* Furthermore, the speed difference between MC and MC .NET is minor (in my view). If your strategy is dependent on this small time difference, you're probably trading with such short holding period that you'd be better of not using MultiCharts at all but a professional, HFT-capable software program.
Agreed, but one of the questions also should be: if I don't know C#/.NET, would becoming proficient in this programming language be a good investment given the possibility of a slight performance gain?
I think the answer is not; you're better off investing in new hardware or buying a second license of MC and running two pc's with MC. Both of these options are a lot cheaper.
The following 2 users say Thank You to Jura for this post: