Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Tue, 2004-04-06 at 02:00, Bob Foster wrote: > It may be problem you're running into with your 401K document is that > Eclipse itself, not just the editors that run in it, is something of a > memory hog. If you're running Eclipse in its default max memory, around > 100MB, any significant work you do will get Eclipse near the limit, > putting you into a constant garbage-collection mode, which slows things > down considerably. > > I personally don't run Eclipse except with the following added to the > command line: > > -vmargs -Xmx256m > > I know this comes as a shock to people coming from emacs or otherwise > unused to running in an all-Java environment not particularly tuned for > low memory usage, but there it is. The question is, do you want to spend > your time optimizing away the need for a <$100 memory chip? > it's not the optimising away the need for this $100 chip, it's the accumulated optimising that counts. and at times going from O(n) to O(log n) techniques. after a while you're not saving 1% on hardware costs (and therefore hardly worth it), but 90% and very much worth it. what would be good is an xml plugin for vi (anyone know one? not just a syntax highlighter) because it seems happy with multi megabyte files. rick <snip/>
|
