Home » JNode handbook » User guide

Hardware requirements

Submitted by epr on Wed, 03/02/2005 - 07:45.

To be able to run JNode, you're hardware should be at least equal to or better then:

  • Pentium class CPU with Page Size Extensions (PSE) feature
  • 256Mb RAM

In order to run JNode the following hardware is recommended:

  • Pentium III 1Ghz or better
  • 512Mb RAM
  • CDROM drive
  • Modern VGA card (see devices)
up
» printer-friendly version | login or register to post comments

Why so much?

Submitted by somerville32 on Wed, 02/15/2006 - 22:48.

Why so much? Is it possible that you could get these requirements down much much much lower? Like 100mhz-300mhz and 64mb of ram?

Cody A.W. Somerville

» login or register to post comments

Reasons

Submitted by epr on Sun, 02/19/2006 - 17:21.

An object oriented system takes more memory then a highly compressed native code OS.
I hope to reduce these requirements, but the numbers you're mentioning will probably never be reached.

Ewout

» login or register to post comments

I have tried running JNode

Submitted by bags on Sun, 03/23/2008 - 10:51.

I have tried running JNode with varying amounts of memory under VMWare. With 256Mb, it locks up in the startup sequence. With a bit more memory, (I think) I saw it try to GC, then die with a NPE. JNode is only relatively stable with 512Mb or more. (Which is sad because I only have 512Mb of physical memory ... and VMWare, X11 and Linux use a fair slice of that.)

I started looking at the way that the GC is implemented, but I have not gotten very far yet.
____
bags

» login or register to post comments

What about...?

Submitted by somerville32 on Mon, 02/20/2006 - 20:36.

What about 333 mhz with 128mb of ram? :]

Cody A.W. Somerville

» login or register to post comments

I hope...

Submitted by epr on Tue, 02/21/2006 - 18:52.

I hope to get the requirements down to 256Mb and 1Ghz with a reasonable performance. Slower CPU's only harm performance, less memory may be a real bottleneck.

Ewout

» login or register to post comments

I believe that the problem

Submitted by ravn on Thu, 02/16/2006 - 22:21.

I believe that the problem is with the quality of the garbage collector (but this is just a hinch)

--
Thorbjørn Ravn Andersen "...plus...Tubular Bells!"

» login or register to post comments

I raise your hinch by one hunch

Submitted by Stephen Crawley on Mon, 10/09/2006 - 17:38.

:-)

Seriously, I think you are right. I have tried running JNode with varying amounts of memory under VMWare. With 256Mb, it locks up in the startup sequence. With a bit more memory, (I think) I saw it try to GC, then die with a NPE. JNode is only relatively stable with 512Mb or more. (Which is sad because I only have 512Mb of physical memory ... and VMWare, X11 and Linux use a fair slice of that.)

I started looking at the way that the GC is implemented, but I have not gotten very far yet.

» login or register to post comments

omg....

Submitted by maiev on Thu, 11/22/2007 - 16:39.

I failed many many many times....tired for tring jnode on vmware. Various problems took place, sometimes the GCThread, sometimes switched to thread invoker, then it had no any process, just stopped, no warnning, no hint

» login or register to post comments

Set the VMWare memory size to at least 512Mb

Submitted by Stephen Crawley on Thu, 11/22/2007 - 20:44.

It works (well enough) for me with 512Mb.

The way I work these days is to do my JNode coding and builds on machine with 1Gb, then scp the ISO across to a 512Mb machine where I run using VMware. Running a 512Mb VMWare on a 512Mb Linux box is not great (the machine gets sluggish due to Linux swapping the VMWare process) but it is good enough for me.

» login or register to post comments