Hi, Unfortunately, I can't get hold of the other machines but I did get it to run on an Ubuntu Linux 8.04 (2.6.24-21-generic Kernel and Gnome 2.22.3) with 512MB RAM and Intel Pentium 4 CPU 2.00 GHz.
I run it at exactly 10am today with 6!:2 'populate ''''' I totally forgot about it and checked back around 3:30pm with it stopped at Current 67 Failed 0 So it run at less than 5.5 hours and the performance went bad starting at 55. I'll try to run it on my Mac (if my son wouldn't use it) when possible. :) r/Alex -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Oleg Kobchenko Sent: Tuesday, October 28, 2008 2:03 PM To: General forum Subject: Re: [Jgeneral] Verb abruptly ends without error > From: David Mitchell <[EMAIL PROTECTED]> > > Oleg Kobchenko wrote: > >> From: bill lam > > > >> On Thu, 23 Oct 2008, Oleg Kobchenko wrote: > >>> >From my experience (steps limit: toSlow - toError). > >>> > >>> Win XP 2GHz 3Gb 32bit 40 - 42 > >>> Vista 2GHz 3Gb 64bit 40 - 55 > >>> Linux VM 2GHz 1.5Gb 64bit 20 - ... > >>> Mac OS X 2.4GHz 4Gb 32bit 60 - 80 > >>> > >>> I concur that Linux was the slowest of all and > >>> Mac was the fastest. > >> IMO "Linux was the slowest" by such a large margin is > >> counter-intuitive, is Linux VM stand-alone or VM ware? > > > > It is Linux in VMware Player under the Win XP. While it's been > > given a generous 1.5Gb of RAM it started getting slow around > > 20 steps much earlier than other systems. > > > > I'd be good to show a result from someone who has a > > physical Linux installation. > > On a native Linux installation, using j64, these were my results: > > Linux64 2x2.2GHz 3Gb 64bit 60 - ran to completion > > It took 3 hours and 18 minutes to finish. It consumed all real memory after 30 > minutes and the system mouse response became seriously erratic after about 50-60 > > minutes. David, this is a very good test. It shows the potential capacity of JDB approach. The slow-down is due to lack of free physical memory and file swapping. We are pushing the envelope here, and hopefully there is some room to optimize JDB. However, there are no miracles: the size of the database plus a certain operational space is required to fit into physical memory to make it efficient, and actually to make any sense for fast efficient in-memory database. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
