Quote from nitro:
[...]
My applications require data to fly from the network adapter into memory and to not to "drop" the quotes. Once a quote is in memory, I unleash CPUs operating at 1 BILLION operations a second at it.
[...]
nitro
Hi nononsense,Quote from nononsense:
Hi nitro,
I have been following your rather costly hardware odysee. You may think that I am a simpleton, but what makes you believe or hope that "unleashing 1 BILLION operations a second" on a big heap of data will give you some kind of an edge?
Be good,
nononsense
Quote from nitro:
prophet,
Can you provide me with a link that shows that the TCP/IP stack is already running at these priorities?
Quote from nitro:
Hi nononsense,
1) It is amazing what we see if we simply open our eyes.
2) The reason for fast CPUs and fast crafted programs is that the "market," like in quantum mechanics, does not like to leave things untidy for "too long."
nitro
Quote from nononsense:
but what makes you believe or hope that "unleashing 1 BILLION operations a second" on a big heap of data will give you some kind of an edge?
Quote from nononsense:
Now as to "the market" properly, nobody can exclude the possibility to crank out some profit by "unleashing one BILLION cpu operations a second" at it. The likelihood of this is not obviously greater than making a profit by unleashing only 0.1 or rather 10 billion ops/sec!
Coming back to your first point: "It is amazing what we see if we simply open our eyes", I would add that unleashing excessive computing power without simply opening our eyes is perilous to profits.
Quote from prophet:
As far as backtesting, it's a HUGE edge. Instead of trying to think about what might work or looking for patterns manually, I find success through finding ways to test the most parameters per second.
For example, I'll take a batch of 17 tick-based system trade lists, generate an intraday tick-based equity series for each system (6.7M ticks over 161 days), and test each of these against 1014 stop loss combinations. This process takes about 16 minutes using highly optimized code, for which the inner loops seem to fit into the L1 cache. I also use some subtle optimizations where I can figure the outcome of certain parameters without testing them.
Quote from nitro:
Hi nononsense,
1) It is amazing what we see if we look.
2) The reason for fast CPUs and fast crafted programs is that the "market," like in quantum mechanics, does not like to leave things untidy for "too long."
nitro