From: Dan L. <dli...@ya...> - 2003-03-14 21:45:21
|
J seems to be a great editor... it has the features and power of Emacs without all the cruft. I'm looking forward to setting it up to do Lisp development in our custom environment here at work. One major problem I've discovered, however, is its memory usage. I'm using 0.18.0 on Windows 2000. When I first start it up (using Java 1.14.1, only commandline option is --no-sessions), it opens the home directory buffer, and it already is using 19.6 Mb of physical memory and 17.3 Mb of virtual memory. Is there anything I can do to tune the memory usage differently? Are there any build or commandline options that control the memory usage? Here is what is in my prefs file: # # Windows # Path separator is semicolon. # Note that double backslashes are required! # ## sourcePath=y:\\src\\jak2\\game docPath=C:\\proj\\j-0.18.0\\doc jdb=C:\\j2sdk1.4.1_02\\bin\\jdb.exe themePath=c:\\proj\\j-0.18.0\\themes theme=Freefloater ## useIncrementalFind=true highlightBrackets=true showLineNumbers=true StatusBar.displayLineCount=true style.comment=2 fontName=Lucida Console fontSize=16 LispMode.files=".+\\.[ejc]l|.*\\.emacs|.+\\.gc" blinkCaret=true LispMode.keywords = c:\\proj\\j-0.18.0\\GoalMode.keywords enableExperimentalFeatures=true Thanks, Dan __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - establish your business online http://webhosting.yahoo.com |
From: Peter G. <pe...@ar...> - 2003-03-15 02:12:11
|
> One major problem I've discovered, however, is its > memory usage. I'm using 0.18.0 on Windows 2000. When I > first start it up (using Java 1.14.1, only commandline > option is --no-sessions), it opens the home directory > buffer, and it already is using 19.6 Mb of physical > memory and 17.3 Mb of virtual memory. > > Is there anything I can do to tune the memory usage > differently? Are there any build or commandline > options that control the memory usage? The short answer is no. The kind of memory usage you're seeing comes with the territory when you're running a Java app with a Swing-based UI. (J tries to make the best of a bad situation by only loading the code for its optional features if you actually use them.) Memory usage shouldn't really be a problem if your machine has enough physical memory to begin with. I'm not sure what the minimum acceptable amount is, and it would depend on what else you're doing, of course. I'm running 512 MB on a Debian box here and never notice any memory- related problems. J also runs fine on my current laptop, which has 256 MB, and on my old laptop, which has 192 MB, and even under VMware on a 192 MB Windows 2000 virtual machine. But you're absolutely right, it needs a lot of memory. -Peter |
From: Dan L. <dli...@ya...> - 2003-03-15 03:01:17
|
Ok. Unfortunately I am developing under another app/environment which assumes memory is somewhat cheap and plentiful ;). We use Allegro Common Lisp to host our language+development environment, and it isn't long before the lisp system has chewed up nearly all available memory, and certain operations will use up all available virtual address space even. We run at the theoretical limit of the Windows memory system (2 Gb per user process). As for garbage collection... its a bit of a joke. We have to restart if it comes to that. Anyhow, I'm looking into adding a mode to J for our language (which is Lisp-like). And then I have to see how to connect J to Allegro CL under windows, which doesn't seem straightforward. Allegro comes with all kinds of Emacs lisp files to help connect it to emacs, so I know there's some work to do... Dan --- Peter Graves <pe...@ar...> wrote: > > The short answer is no. > > The kind of memory usage you're seeing comes with > the territory when > you're running a Java app with a Swing-based UI. (J > tries to make the > best of a bad situation by only loading the code for > its optional > features if you actually use them.) > > Memory usage shouldn't really be a problem if your > machine has enough > physical memory to begin with. I'm not sure what the > minimum acceptable > amount is, and it would depend on what else you're > doing, of course. > I'm running 512 MB on a Debian box here and never > notice any memory- > related problems. J also runs fine on my current > laptop, which has 256 > MB, and on my old laptop, which has 192 MB, and even > under VMware on a > 192 MB Windows 2000 virtual machine. > > But you're absolutely right, it needs a lot of > memory. > > -Peter > __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - establish your business online http://webhosting.yahoo.com |
From: Peter G. <pe...@ar...> - 2003-03-15 03:30:12
|
> Unfortunately I am developing under another > app/environment which assumes memory is somewhat cheap > and plentiful ;). We use Allegro Common Lisp to host > our language+development environment, and it isn't > long before the lisp system has chewed up nearly all > available memory, and certain operations will use up > all available virtual address space even. We run at > the theoretical limit of the Windows memory system (2 > Gb per user process). As for garbage collection... its > a bit of a joke. We have to restart if it comes to > that. > > Anyhow, I'm looking into adding a mode to J for our > language (which is Lisp-like). And then I have to see > how to connect J to Allegro CL under windows, which > doesn't seem straightforward. Allegro comes with all > kinds of Emacs lisp files to help connect it to emacs, > so I know there's some work to do... Well, in some sense j supports Lisp shells. I typically run Allegro under j, and there are ways to send defuns and/or selected regions directly from a j source buffer to the Lisp process (evalRegionLisp, mapped by default to Ctrl Alt R, and evalDefunLisp, mapped by default to Ctrl Alt E in Lisp mode buffers). Unfortunately this is not documented well (or maybe at all, except for the source in LispShell.java and LispShellMode.java), and in the general case it requires jpty, which on Windows requires Cygwin... If you want to take a look at this, you should get the lastest 0.18.0+ development snapshot: http://armedbear.org/j.zip (source) http://armedbear.org/j-jar.zip (just j.jar) You'll need the source in j.zip if you want to build jpty (it's not part of the binary distribution). Alt X, "lisp" will run j's built-in toy Lisp, whose only real virtue is that it doesn't require jpty... ;) This stuff is currently under heavy development and for the most part was not in the 0.18.0 release. -Peter |