Search results

  1. P

    Who exactly is buying?

    Your thinking is very similar to mine (though I know nothing of south america,I believe what you say). But for the sake of objectiveness, it could be that Bernanke is doing things better than those dictators. You can never assume that the same thing done by different people has same outcomes...
  2. P

    IB TWS taking a lot of memory

    today I tried 933.5 for hours: I used it to trade,then had to go away,then returned:in a total of 5 hours, memory usage is always 140-145 MB. Program is getting quotes and 1-second historical data for futures and forex. heap size being 96MB, maybe gc is sweeping memory,but I always see 0%,1%...
  3. P

    Excel and FIX for algo autotrading

    I speak about Excel 2000,I don't know recent versions but I don't think the principles have changed. VBA is a visual COM version of Basic inserted in an Excel object model.As such, you can do whatever you want with it,and there various ways of doing the same thing.You can even use system API...
  4. P

    Who exactly is buying?

    Japan index buyers in december 1989 have now 1/3 of their initial value; Nasdaq index buyers in 2000 have a good cut too, and also 2000 buyers of many other indexes (Italy for example is less than 1/3). DAX, Dow and S&P index buyers in 2000 have a very small gain in 13 years. In my opinion...
  5. P

    Who exactly is buying?

    Volume/volatility have been great most of the time from 1997 to 2000. When we reached the top in 2000, volume was high,volatility even higher. On the other hand, volume/volatility have been low most of the time from 2003 to 2007 and from 2010 till now. I believe volume/volatility are...
  6. P

    IB TWS taking a lot of memory

    ddecker, this is not a matter of API: I connect to Gateway directly with a TCP/IP socket the same way java and C++ clients do in the IB API package. I download 2000 seconds (the maximum allowed) per historical data request. regulus, if ib doesn't pay attention,post it here and I'll try to...
  7. P

    Today is the day

    In my opinion this is not "no volume", but "low volume".What is strange is lack of volatility,prices often move in straight lines. I think there is no point in discussing about market manipulation by the FED:Bernanke told they do it both indirectly (QE) and directly (yes,he once said that)...
  8. P

    Fed will start tapering QE in September

    holding to maturity before buying new assets means stopping QE without exiting. stop=don't inject new liquidity anymore exit=get the injected liquidity back I don't think they can stop QE now, they never will in my opinion,without crashing the economy. It's exactly like drug
  9. P

    Fed will start tapering QE in September

    The FED voluntarily exiting QE is like having reverse gravity on earth, to me. If it happens I'll be the first to buy the ticket for the show.
  10. P

    Extremely High Margin Requirements on Back Months - Interactive Brokers

    I don't know if there are hidden reasons behind this decision,but the liquidity problem is a real problem for a broker if he wants to take care of emergency situations. In 1929 and 1987 crashes, all of a sudden there was noone to sell to. "Sell,sell,sell!!!" "To whom?" was the talk between...
  11. P

    IB TWS taking a lot of memory

    Just to be precise, here are the switches I use: -Dsun.java2d.noddraw=true -Dsun.java2d.opengl=false -Dsun.java2d.pmoffscreen=false -Xmx96M
  12. P

    IB TWS taking a lot of memory

    regulus, I use only 1 sec. data,so I'm in the same case as you are.I have 1 GB of memory and set java heap to 96 MB. So I don't understand why my problem is much smaller than yours (actually I have no problem)
  13. P

    IB TWS taking a lot of memory

    Is tick data available with IB? I never heard of it,I looked in the documentation and found no mention of it
  14. P

    IB TWS taking a lot of memory

    Well,if the only thing that changes between us and regulus is the 64bit type OS,maybe there lies the problem. As I wrote,I know java very little,and I don't think customers (who are not supposed to be programmers) are expected to dig into GC. I won't ask IB as I don't have problems,I tried...
  15. P

    IB TWS taking a lot of memory

    Of course it is only a workaround. I hoped it could stop memory growing some time after crunching,but if you have to set a threshold then it means that memory consumption doesn't stop. There are a lot of memory optimizers which generally have time and memory thresholds to set,but I don't know...
  16. P

    IB TWS taking a lot of memory

    (EDIT: I wrote this post before reading regulus reply; regulus, did the optimizer help?) Thanks for your information,ddecker,but it seems you didn't read what regulus wrote. 1) The problem is just from 933.5 onward, so 930.5 is known to work right. If you want to help, why don't you try on...
  17. P

    IB TWS taking a lot of memory

    Wait, ddecker is right when he says that it's not enough to seriously confirm a memory leak. But I think the difference in behaviour is clear (even if I didn't write it,I watched carefully what happened to memory usage while software was working),and should be enough to start an investigation...
  18. P

    IB TWS taking a lot of memory

    I'm not obsessed by memory consumption,I was just replying to regulus who had a more serious problem. These are tests for him (see his last posts). I don't know why his figures are so much bigger than mine,I was just noting that 933.5 has a different behaviour than previous versions. I don't...
  19. P

    IB TWS taking a lot of memory

    Tried 933.5. I forgot to tell java version:1.6.0_45.I think I read somewhere that IB advises to use 1.6 instead of 1.7. Gateway memory consumption: 123 MB My application memory consumption 30 MB I see that when it downloads additional data (every 30 mins each security) memory increases...
  20. P

    IB TWS taking a lot of memory

    I give you anyway my current numbers with 917.9,then I'll try with 933.5. Operating system is Windows 7. Getting historical data for 13 securities. Gateway memory consumption: flows around 85 MB My application memory consumption: 30MB
Back
Top