Quote from NetTecture:
Learn maths. NxCore does it. THere is nothing against it.
Assume:
1000 symbols
100 updates per second
That is an astonishing 100.000 updates. A lot?
Hm, bandwitch on a 6mbit link is around 600.000 bytes per second - and 6Mbit are not exactly a lot by todays standard.
This is 6 bytes per update. I have encoded ticks in a LOT less.
Plus, with all respect, 100 updates per second will not happen on all 1000 symbols. You most likely use less than 1mbit even during active hours.
Basic math.
Processor wise - how do you assume that 100.000 packets decoded and passing through will even stress one processor core? Hint: They do not![]()
All true .... to a point. It's what you do upstream with the data that may or may not stress your processing and/or storage facilities.
I have no trouble whatsoever in handling 500 high volume stocks Level I off IQFeed which claims to supply every tick. Can't even keep one core of a 9550 quad busy. Java application. I have never even profiled the code for performance as it is not an issue.
In fact most of the CPU utilization is for "christmas tree" - quote sheet - tables.
Having said that 1000 Level 2 instruments could be another matter altogether, requiring some serious design for performance. Depends on what you want to do with the data.