Quote from zmax:
HFT,
Are you using the so called ultrafast/low latency mkt data feeds or creating your own orderbooks from all the connections you have to all banks/brokers out there. If using mkt data feeds can you name the fastest for fx, fut markets?
thank you!
Quote from xbaha:
Hello,
Thanks HFT for the valuable information, i hope you are still around to answer my questions:
1. how long in a calm market it takes in ms or micro sec from the time you send the order, until you receive confirmation of a fill?
2. i would like to know more about the risk profile, how many ticks would be a maximum stop loss for an HFT in average?
3. this could be a stupid question, but i heard that HFT can be tricked to buy @ ask , sell @ bid, and they would do it over and over again, what would be the kind of strategy that tricks HFT to do such a thing?
Thanks.
. Seriously though, flipping a sign somewhere in your code can have this effect, though it's usually mitigated by some risk limit down the line. As far as tricking someone else's HFT, your guess is as good as mine.Quote from murphmack:
And how does HFT dink around with the open/close auctions? Any hints?[/B]
Quote from hft:
About backtesting, there are a small minority of people in HFT that lean on backtesting results in market-making, but I am not one of them. [/B]
My definition of backtesting might not match yours. I define it strictly as simulating how a strategy performs through historical data. It's really hard to do this well with a high-frequency market-making strategy. Instead of that, I rely other forms of analysis (and admittedly 'educated guesses').Quote from lastlook:
HFT, this sounds quite odd. How else would you be able to develop and debug a new strategy, improve an existing one, or know that you have sufficient edge to startup the entire operation?
Quote from hft:
My definition of backtesting might not match yours. I define it strictly as simulating how a strategy performs through historical data. It's really hard to do this well with a high-frequency market-making strategy. Instead of that, I rely other forms of analysis (and admittedly 'educated guesses').
- Run blind: Simply rest small size and see if it makes money
- Trial and error: Tweak some settings and run it concurrently with a control strategy to see if it's more effective.
- Post-trade analytics: Analyze the trades you got into in order to improve the strategy.
- Historical data analytics: Analyze historical market data, but not necessarily simulated fills as in a typical backtest.
Some of that is quite vague, which is both to not reveal secrets as well as indicative of the ad-hoc nature of the process anyway.
This is something I discovered for myself some time ago. Less experienced traders often look to backtesting to tell them how an idea will turn out if they implement it. Testing doesn't do that very well, and especially not with HFT. Testing can sometimes tell us when an idea is really bad. I believe achieving alpha starts with intuition, and that takes experience.Quote from hft:
My definition of backtesting might not match yours. I define it strictly as simulating how a strategy performs through historical data. It's really hard to do this well with a high-frequency market-making strategy. Instead of that, I rely other forms of analysis (and admittedly 'educated guesses').