NexusFi: Find Your Edge


Home Menu

 





MultiCharts 8 64-bit


Discussion in MultiCharts

Updated
      Top Posters
    1. looks_one Big Mike with 6 posts (8 thanks)
    2. looks_two diverdan with 3 posts (1 thanks)
    3. looks_3 Lampert with 3 posts (0 thanks)
    4. looks_4 Jura with 2 posts (0 thanks)
      Best Posters
    1. looks_one Bimi with 2.5 thanks per post
    2. looks_two xevian with 2 thanks per post
    3. looks_3 theorist with 1.5 thanks per post
    4. looks_4 Big Mike with 1.3 thanks per post
    1. trending_up 20,354 views
    2. thumb_up 26 thanks given
    3. group 15 followers
    1. forum 32 posts
    2. attach_file 0 attachments




 
Search this Thread

MultiCharts 8 64-bit

  #31 (permalink)
Bimi
London
 
Posts: 118 since Mar 2010
Thanks Given: 42
Thanks Received: 58


theorist View Post
Anyone know what the RAM requirements are for this program? I.e., suppose you want to import, chart, and backtest a 5 GB historical tick data file; how much RAM does MC draw on to do this? I ask because I've seen a program that needs to have available RAM equal to to about 10x the size of the file you are importing; so with, for instance, 16 GB of RAM (leaving 15 available after the system), you are limited to importing and working on about a 1.5 GB tick file.

First, you don't have to have a lot of memory to load a large data set, because the Windows operating system would swap the data to disk if it can't all fit into memory. It will recall the data from disk only when needed.

If you are talking about loading the data alone (ie without indicators), and you would want to have everything resident on memory, then you would need at least twice that amount. The memory need goes up exponentially after that; it depends on how many variables you have, how many and how big are arrays. Because each variable requires a memory location for the entire series of the data you have loaded. (note: loaded by MultiCharts. Not what is in your database).

Reply With Quote

Can you help answer these questions
from other members on NexusFi?
Better Renko Gaps
The Elite Circle
NT7 Indicator Script Troubleshooting - Camarilla Pivots
NinjaTrader
Are there any eval firms that allow you to sink to your …
Traders Hideout
ZombieSqueeze
Platforms and Indicators
Exit Strategy
NinjaTrader
 
Best Threads (Most Thanked)
in the last 7 days on NexusFi
Get funded firms 2023/2024 - Any recommendations or word …
61 thanks
Funded Trader platforms
39 thanks
Battlestations: Show us your trading desks!
26 thanks
NexusFi site changelog and issues/problem reporting
26 thanks
The Program
18 thanks
  #32 (permalink)
 theorist 
Los Angeles, California, USA
 
Experience: Beginner
Platform: TradeStation, AmiBroker
Trading: ES
Posts: 9 since Jun 2012
Thanks Given: 17
Thanks Received: 11


Bimi View Post
First, you don't have to have a lot of memory to load a large data set, because the Windows operating system would swap the data to disk if it can't all fit into memory. It will recall the data from disk only when needed.

Thanks, Bimi.

That's not the way AmiBroker works, but it sounds like MC is different -- for AB, if you want to import a data set, it needs to load the whole thing in RAM. Besides, if you actually want to do anything with the data (backtest, etc.), wouldn't you need the entire thing to be resident in RAM, simply to get decent performance? I.e., if it needed to swap to a disk, even if you have an SSD, wouldn't that slow things to a crawl? [See, for instance, this discussion of disk vs. RAM vs. cache access, by the developer of AmiBroker, at the end of this link: https://www.amibroker.com/guide/h_multithreading.html]


Quoting 
If you are talking about loading the data alone (ie without indicators), and you would want to have everything resident on memory, then you would need at least twice that amount. The memory need goes up exponentially after that; it depends on how many variables you have, how many and how big are arrays. Because each variable requires a memory location for the entire series of the data you have loaded. (note: loaded by MultiCharts. Not what is in your database).

OK, sounds like MC's memory demands are similar to AB's.

Reply With Quote
Thanked by:
  #33 (permalink)
Bimi
London
 
Posts: 118 since Mar 2010
Thanks Given: 42
Thanks Received: 58



theorist View Post
Thanks, Bimi.

That's not the way AmiBroker works, but it sounds like MC is different -- for AB, if you want to import a data set, it needs to load the whole thing in RAM. Besides, if you actually want to do anything with the data (backtest, etc.), wouldn't you need the entire thing to be resident in RAM, simply to get decent performance? I.e., if it needed to swap to a disk, even if you have an SSD, wouldn't that slow things to a crawl? [See, for instance, this discussion of disk vs. RAM vs. cache access, by the developer of AmiBroker, at the end of this link: https://www.amibroker.com/guide/h_multithreading.html]

OK, sounds like MC's memory demands are similar to AB's.

If you are backtesting, you DO NOT need to load ALL the data into memory.

NO, it does not slow things down. Swapping is fast, especially in backtest environment where real time data is static.


I don't know how AmiBroker memory works. It is supposed to be very good with backtesting. When it comes to optimization, it is not as fast as MultiCharts, but the backtesting is supposed to have good performance.

Reply With Quote




Last Updated on July 21, 2012


© 2024 NexusFi™, s.a., All Rights Reserved.
Av Ricardo J. Alfaro, Century Tower, Panama City, Panama, Ph: +507 833-9432 (Panama and Intl), +1 888-312-3001 (USA and Canada)
All information is for educational use only and is not investment advice. There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
About Us - Contact Us - Site Rules, Acceptable Use, and Terms and Conditions - Privacy Policy - Downloads - Top
no new posts