It's pretty real world for me. The server offers coalesced data from Zacks, TradingEconomics, ETFdb, the Federal Reserve, the US Commodities Futures Trading Commission and about 10 other sources for consumption by our systems. Against that server, I'm running hundreds ETF models daily, each of which loads about 10 time series for each of 50 to 3000 stocks, each of those with years of data.
Currently, I've fired up a second cloud sibling to the production C++ box. The new Racket code there is running well, not much faster in total though, because the processes that crank on the data have not changed (C++ with Python on top). The runs are just short of two hours. The only downside that I see is that I'm using 300 megs of RAM against the C++'s 60. By the way, I've also discovered considerable improvements in database access and FFI speeds, so hats off to those guys too. Thanks again, John Griffin On Thu, Sep 24, 2015 at 10:52 AM, Matthias Felleisen <matth...@ccs.neu.edu> wrote: > > On Sep 24, 2015, at 5:59 AM, JCG <griffin...@gmail.com> wrote: > > > I have no idea what networking implementation facts have changed between > 6.1 and this snapshot, but it's now about 20% faster than the C++ server. > The reimplemented service will remain in Racket. > > > > Wow. Did you test under ‘real world’ circumstances or is this based on > ‘micro benchmarks’? > > > Thanks to whomever it was that jacked up the networking speed. > > > No kidding. > > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
