I believe it is a fixed number of strstegies per thread, and one thread per core, or something to that effect. On Jun 26, 2013 2:03 PM, "Xue-Feng Yang" <[email protected]> wrote:
> So you mean JBT running for each strategy in one independent thread, > instead of running by a fixed number of agents/workers. > > Anyway, I will look into the details later. > > Than you very much, > > Xuefeng > > On Wednesday, June 26, 2013 4:54:39 PM UTC-4, Eugene Kononov wrote: >> >> >> Eugene: you said "The behavior that you described is exactly how >>> JBookTrader was designed". Do you mean you actually have a piece of code to >>> control this? Or you just put the calculations in many threads? >>> >>> >> The optimizer is multi-threaded, running many thousands (or even >> millions) of strategies simultaneously. So the full CPU utilization >> happens naturally. >> > -- > You received this message because you are subscribed to the Google Groups > "JBookTrader" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jbooktrader. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jbooktrader. For more options, visit https://groups.google.com/groups/opt_out.
