sidhartha70, i guess the difference here is the number of bars you are using. In my main database I am running 1 minute databases and would like to be able to see several years worth of data. This requires a large number of bars loaded, on the otherhand, the other database will only require a few days worth - just enough to run some up-to-date averages. The latter will be used for realtime monitoring only.
I think I resolved the crash with IQFeed. Initially I was running 2 instances of AB using RUNAS. The reason is that I wanted to have different preferences on each instance (which as far as I know cannot be done if running as the same user), however when these two talked to the same instance of IQFeed, IQFeed crashes frequently. I then repeated the test by launching 2 instances of AB as the same windows user and I have not crashed until now. This was only in the last few hours of the US Market yesterday so I will carry on testing today. cheers, eToke --- In [email protected], "sidhartha70" <sidharth...@...> wrote: > > eToke, > > I use something approaching your setup, but under one instance of AB. I have > 8 charts across 2 monitors. 5 different layout which allow me to switch very > quickly depending on exactly what I want to look at. > > My AB runs like a song... I wish I could utilize more of the 8 cores I have > on my PC, but it does run quickly. > > The single biggest factor in processing speed is the number of bars in your > DB. In my intraday DB which I use for day trading I have 25,000 bars max. > > How many bars do you have in your DB...? > > --- In [email protected], "etoketrader" <etoke@> wrote: > > > > I was thinking the advantages would be the following: > > 1) The split of processing load as you mention > > 2) In order to run market internals, I need to display several charts for > > several instruments at once: > > - Tick > > - AD Line (this needs a few instruments actually to build correctly) > > - Interest Rates (that's 5 yr 10yr and 20yr > > - SPY/QQQQ/IWM > > - Market Sectors (XLU,XLP,XLE etc..) > > ...and so on. This produces a huge load on the total chart refresh rate, > > making subsequent operations such as scanning, switching symbols and so on, > > slower. I was thinking that if I could separate all this stuff into another > > instance (separate database with ONLY required symbols, much shorter > > history such as 10 days instead of 10 years!), then I can get this realtime > > display and have my main AB running like a song. > > > > I have tried it this US market morning and THE PROBLEM I am encountering, > > however is not AB! IQFeed client is crashing on me when i try this > > configuration. Apparently it doesn't like it. I am not sure whether to > > continue the tests or find another route. > > > > cheers, > > eToke > > > > > > > > > > > > --- In [email protected], "sidhartha70" <sidhartha70@> wrote: > > > > > > eToke, > > > > > > What exactly is the advantage of running two instances as opposed to > > > having more chart windows under the one instance...? > > > > > > The only advantage I can see is that if you are running multiple cores it > > > splits the processing load more effectively...?? > > > > > > > > > > > > --- In [email protected], "etoketrader" <etoke@> wrote: > > > > > > > > I normally run one instance of AB which displays my "main" section - > > > > charts on the instrument I am working on at the moment, as well as a > > > > "market internals" section which shows charts of the major indices, > > > > tick, trin etc.... > > > > > > > > I am trying a small experiment in order to see whether things run > > > > smoother. I am trying to run 2 instances of AB for the two sections I > > > > mention above. I am not sure whether this will make things better but > > > > currently the fact that I am simultaneously charting several symbols at > > > > once is putting additional load on my setup. > > > > > > > > My question: Some symbols exist in both instances. Will the fact that > > > > the two instances are connected to the same IQFeed and that separate > > > > backfill requests are assigned to the same IQFeed instance mess things > > > > up or is it a good proposition to work this way? > > > > > > > > thanks and regards, > > > > eToke > > > > > > > > > >
