>
I don't believe it is discussed anywhere. However, it is pretty clear that
if Eclipse is setup to do less then it will be faster. For example, turning
off automatic building can speed Java development since you don't have any
background threads compiling your code. You can also remove the outline,
task, problem, error, etc panes, which are updated in real time. I tend to
either minimize them or make them fast views, so they are there when I need
them, but aren't being redrawn when I don't.
> How Do I provide addl resources?
>
You can use the standard java command-line switches to change the amount of
memory Eclipse has access to.
> Safari 2 windows open -- no applets, swf or animation
> Mail 2 windows open
> Activity Monitor
> Terminal 3 windows
> Eclipse
> MySQLd
> JRun
> CFMX61
> 75 processes, 275 threads
>
I imagine that 1GB of RAM isn't enough for all that. I would recommend 2GB
of RAM.
> And Eclipse still seems slow -- takes .75 sec to switch windows or tabs
> -- small programs, windows side-by-side, no overlap.
>
I see no noticeable delay.
> It isn't bad -- just slower than I am used to -- slower than BBEdit,
> much faster than DW, similar to JEdit.
>
.75 sec is bad in my book.
> The way D&D works in BBEdit and other apps (like Mail, etc) is this:
>
> 1) Select some text & release the mouse button.
> 2) Click-hold within the selected text
> 3) drag & release the mouse button to drop.
>
Oh, you want D&D text; I thought you meant files.
-Matt
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
