Great pointer. With the motif of keeping the balls in the air: disk is bad, in-memory database and caching is good.
Another point is productivity offsets scripting system, due to IO latency. One observation not realizable in J: worker threads significantly beat worker processes. That might be compensated by overlapped IO (system thread pool). Also nice is reusing hybernated partially pre-calculated state. That where stored (or cached) WS may be useful. Oleg Kobchenko On Jul 16, 2007, at 12:47 PM, Robert Bernecky <[EMAIL PROTECTED]> wrote: I just watched this video by one of the YouTube designers. It neatly captures the benefits of rapid development, and of the problems of being behind the eightball on system load: http://video.google.com/videoplay?docid=-6304964351441328559 Bob ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
