I have downloaded the latest Eclipse IDE, Galileo, and tested it to see if it good for developing web applications in Java. I have also tried the Ganymede version of Eclipse and find that is it also good.
My Problem is that sometimes it hangs and stops responding while I am developing. Sometimes when I open a file, Eclipse hangs and does not respond for awhile. It seems that Eclipse is going slower and my job is getting slower because of the time that I am spending waiting for the response of Eclipse.
When I went to NetBeans 6.7, it was good and the performance was good. The loading is faster and the IDE responds well during my development testing.
My computer has 1 GB of RAM and a 1.6 GHz CPU.
What can you say about this?
I'm using Eclipse PDT 2.1 (also based on Galileo) for PHP development, and I've been using Eclipse-based IDE for 3 years now ; my observation is that 1 GB of RAM is generally not enough to run Eclipse + some kind of web server + DB server + browser + other stuff :-(
I'm currently working with a 1GB of RAM machine, and it's slow as hell... Few months ago, I had a 2GB of RAM machine, and things were going really fine -- and I'm having less software running on the "new machine" than I had on the other one !
Other things that seem to affect Eclipse's responsivness is :
opening a project that's on a network drive (accessing the sources that are on a development server via samba, for instance)
sometimes, using an SVN-plugin like SUbversive seems to freeze Eclipse for a couple of seconds/minutes
A nice to do with languages like PHP (might not be OK for JAVA projects, though) is to disable "automatically build" in "project"'s menu.
As a sidenote : I've already seen questions about eclipse's speed on SO ; you might want to try so searches, to get answers faster ;-)
This is a common concern and others have posted similar questions. There are optimizations that you can perform on your Eclipse environment. Take a look at the solutions posted here.
netbeans is really damn hot, i just didn get it to automatically release my android projects...
thinking of features.. i'd prefere eclipse...
to fasten it up a little more, just disable 'automatic build' doesnt really change anything (build just takes a little longer)
but it's really feelable faster...
but, after 1 or 2 hours, i also have to close, wait, and re-open it.
kind of sucks... (gotta macbook pro, 2.26 (i think) ghz, 3gb ram,
gave it a minimum of 768MB of ram, and keeps getting slower..
really sucks
::edit::
I also realized, that after opening a XML file, eclipse instantly gets a little bit more laggy (already disabled XML live compiling, or something similiar, makes no difference :( )
Our machines are bigger : 2GB ram, and faster CPU.
I'm sure that, as all software, Eclipse gets bigger and slower when upgrading version, due to all new functionnalities included. The good news is that from time to time, a release also brings some notable performance improvement. But in my experience, each time I tried using a ten-year old software on my current machine, it was lightning fast, so I'm sure the tendency is to get slower. I agree that this is a sad for us, when we don't get a better machine.
There might be some things you can do, to improve the responsiveness of your Eclipse.
I don't know if you already tried everything ... ?
My experience has been that NetBeans, Aptana, and Komodo are fast on computers where Eclipse is painfully slow. Maxing out RAM has seemed to help. Any chance you can bump up to 2 gig?
Netbeans sped up quite a bit in the last few years, perhaps your comparison is relative to the speed of netbeans?
Lately I had to up the size of my eclipse -Xmx from 64mb and decided I might as well go to 512, and it got a bit chunkier. at 64 I never saw the slightest pause, when it actually NEEDS a collection at 512 because of a long-running process that's not letting the background GC thread run, it can get a little pausey
I'm running on a pretty old version of eclipse (customized by the cable industry so it can run and display cable apps on a TV emulator) so your mileage may vary.
Check if you can disable unwanted plugins during start up.
Related
I just bought my first Mac Book Pro (i7, SSD, 16GB RAM), I've installed Eclipse STS and realized that the performance is terrible.
For example, when I save 2 or 3 files in 5 seconds, the program crashes and after 3-4 minutes it responds again but very slowly and I have to restart it. The performance improves a lot if I turn off the Build Automatically...but I find it very sad.
I've been working with my old PC (i7, 8GB RAM and normal HD) and the performance is much better. I'm considering returning the Mac and buying a new PC.
Before installing STS I had installed the latest version of JDK.
My question is if there are any Mac settings missing for STS to work properly.
I found the solution here.
Since I removed this line from STS.ini:
-Xverify:none
The performance has improved remarkably even with Build Automatically enabled.
To my experience, STS is a heavy tool designed for Spring projects. Auto build option will only make the tool hang and system will freeze. Better you can disable that option and use the tool. There's no problem with your Max book AFAIK.
I know this has probably been asked many times before, but I still haven't seen an actual fix for it.
My day-to-day development environment is as follows:
1. NetBeans (latest), 2. Glassfish (latest as bundled with NB), 3. JPA, JSF, JAXB, Jersey for JAX-RS
I have about 600 classes in my project, spread across two EJB projects and one WAR project, all inside an EAR.
I am on latest JDK 7 (on OS X) and I am on an hourly basis getting the infamous "PermGen space" bug. Let's say if I am doing 3 incremental re-deploys a minute, I can only work for a short while before either:
Glassfish run out of PermGen space, so I just have to kill the process.
Deployment becomes extremely slow, due to me having increase max permgen space (as one is advised to do from dozens of answers on S.O.)
Often the only solution is to kill glassfish every 30 minute or so. It's definitely due to a bug somewhere that simply loads new classes for every new incremental re-deploy instead of getting rid of the old ones. I thought this was supposed to be fixed in JDK 7?
This has been a long standing bug in the kind of development environment, and I am rather shocked that it's still going on after my 5+ years of Java development. It's just so frustrating and incredibly unproductive.
(Just before anyone suggests increasing permgen space, believe me I've tried that, and the only thing it "solves" is to prolong the inevitable. I've seen redeployments take up to 400 seconds at its worst. Redeployment is supposed to take 5-6 seconds for a project this size, no more.)
EDIT: I ran jmap and jhat on the Glassfish process after the following steps:
Start glassfish
Deploy my EA
Undeploy my EA
Then did a heap dump with jmap
It turns out that all my classes (which should have been unloaded) are still loaded! Hopefully this is useful information to someone reading this...
Surely, that is a bug, and I don't think that there is an easy solution for that. (If there were, probably you have had it already).
What you can try: Use some hot code replacement tool for example JRebel, This way you don't have to deploy all the time, instead this tool watches the changes of the .class files (and even other web resources, if you configure so), and replaces the class definition within the running JVM. Sounds cool, right?
It works as a Java agent, it starts when your JVM starts.
There are 3 drawbacks of this solution: The deployment is a bit slower, it's harder to debug, and it's a proprietary software (but does not cost much)
When developing with Netbeans + Glassfish and using "Deploy on Save" we've found that libraries packaged within an application are not unloaded when the project is re-deployed; this causes GF to slow down and quickly run out of memory.
Try de-selecting "Package" for all compile-time libraries and place those not already in the Glassfish classpath in the domainX/lib directory.
Not sure but this may be related to GLASSFISH-17449 or GLASSFISH-16283.
The auto complete stalls so frequently and for so long, I quit using it altogether.
I've had success with the following using Eclipse (Classic) 3.6.1 on Windows 7 x64.
"A workaround, until the fix is released in 3.6.2 is summarized here: http://groups.google.com/group/android-developers/msg/0f9d2a852e661cba"
(copied for convenience)
"You can replace your /plugins/
org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar plugin with one from
http://www.google.com/url?q=http://adt-addons.googlecode.com/svn/patches/org.eclipse.jdt.core_3.6.1.v_A68_R36x.zip&ei=vg5aTf2RIMrUgAeI-qTvDA&sa=X&oi=unauthorizedredirect&ct=targetlink&ust=1297749446528273&usg=AFQjCNFv7FGlTrnoVhRGE35JPjHxOwI_Bw
and restart Eclipse. Content Assists will be much better. Just try it.
Don't forget backup your original plugins. "
This solved part of my problem.
In preferences, I defaulted all the 'Java->Editor->Content assist' screens and the performance is much improved. Any lag I have now is due to system speed and is negligible. I've gone from minutes to seconds building the suggestion list.
UPDATE: This didn't completely solve my problem, but it got me close. The search continues...
UPDATE: I'm developing in Java for Android using the default packages that are included and any that might have come down during a update(in retrospect, maybe choosing update all in the SDk update might not have been wise). The timing is fairly consistent online and offline. I did a few tests and found the following:
Startup Eclipse and enter a line of code that can use a .toString(). Typing the '.' populates the auto complete within 2-3 seconds. Type a 't' and it takes 70-75 seconds. After that, 10 seconds. Diff objects do the same thing(75 the first time, 10 after that). It's the filtering process that appears to stall. My CPU does not max, Memory is OK, but the program will go not responding till it's done. Any typeahead gets cached and eventually filters the list when Eclipse starts responding.
For me the problem went away when I increased the memory for the vm.
Put this in your eclipse.ini:
-Xms512m
-Xmx1024m
on my 4GB Windows Vista system this would happen A LOT !! (as well as debug issues when looking up variables).
This all went away after I built my new PC with 8GB RAM. I can now run 4 emulators simultaneously and it doesn't have any debug problems any more either. Auto complete with huge lists also works just fine.
it would seem to be just an issue with how much RAM you've got.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
How far MacBook Air is suitable for developers?
Can it handle running Eclipse, JDK, Flex Builder, Apache, Tomcat and couple of usual applications together and still perform well ?
Or is it purely for business people?
Suitable yes in the sense that it is above the "minimum system requirements". I've ran (older) versions of Eclipse and J2EE on much slower machines. I still recoil when I think of the time I tried to build distributed Eclipse plug-ins on an IBM T20.
Are you going to enjoy it and be very productive on it? I would bet not. You probably want more cores, more memory, etc. Developers are also prone to loss of concentration, so an added delay when switching windows, starting debugs, etc. will affect your performance.
In addition, I would highly recommend against trying to do full-time dev on a 13" screen. If you have to use your laptop screen, go with at least 15" with a decent resolution. IDEs require resolution these days because of the sidebars.
For about the same cost you can get a 15" MBP, better bang for the money. Core i5 in the new MBPs is also better structured for multithreading, IMHO, than the core 2 duos.
I have been using a 13" MB (before they became pros) with 4GB/2GHZ Core 2 Duo for some time now for work with Eclipse, XCode, Cassandra, Apache/Tomcat and Photoshop. Here is my take away:
Screen size: At times I wish I had more but you learn to become a minimalist with all the windows available and use the hiding option on most of them. Major annoyances are typically having to go back and forth between dev environment and Console. Most of the time I code from home where I have an external monitor which solves all of this.
Speed: The CPU is sufficient but the memory is not if you're doing major dev work with Java. Java is a memory-whore. I started with 2GB but had to upgrade to 4GB. Typically this was when I was working with Eclipse and had the whole stack running on my machine (app server, data store, dev environment). I've read that MBAs are upgradable to 4GB but it's soldered on in which case you should order the upgrade directly from Apple to be safe (whereas with MBPs you can do it yourself no problem).
Convenience: My 13" MB is light. But, I don't know if it's age or spending too much time coding, I find myself wishing it was even lighter especially when I fly somewhere.
All in all, I'd be willing to switch to a MBA if cost weren't an issue. Another thing to keep in mind is that you'd have to be OK with working on high-resolution laptop on a smaller screen. It's worth going to the Apple Store to see it with your own eyes.
What about the new MacBook Air Model? The 13" inch version with 4GB RAM and 2,x GHz cpu should do it.
The SSD/FLash will be the performance booster in this model.
I used to do software development on an iBook with a 1.42GHz processor and 1GB of RAM, so I'm pretty sure the MacBook Air will be more than adequate. :)
To give a more technical analysis: The Air has a relatively slower processor than, say, a MacBook Pro, and less RAM (in its standard configuration), but it should still be more than adequate for development work.
Whether the MacBook Air is worth its price tag (especially compared to a MacBook or MacBook Pro) is a different story. :)
I'd say that if you're happy to consider using a laptop as your development machine then you'll probably be fine with a MacBook Air.
In my opinion, monitors, mouse, keyboard far outweigh any processing power.
I've got one. It's pretty fast, the SSD makes a lot of difference compared to the standard MBP laptops. I run IntelliJ on it. MBP is a bit faster with building the projects and I feel that IntelliJ sometimes is a bit sluggish, but it's OK.
I think it's a proper dev machine. We're typing text most of the time :-) We're not rendering video or 3D scenes. All devs I know that have one, are really happy with it. So yes, but it.
I just get the beach ball all day long (it's been doing nothing for hours). It's not taking CPU, not reading from disk, not using the network.
I'm using Java 1.6 on Mac OS X 10.5.4. It worked once, now even restarts of the computer won't help. Activity Monitor says it's "(Not Responding)". Only thing that I can do is kill -9 that sucker.
When I sample the process I see this:
mach_msg_trap 16620
read 831
semaphore_wait_trap 831
An acceptable answer that doesn't fix this would include a url for a decent free Oracle client for the Mac.
Edit:
#Mark Harrison sadly this happens every time I start it up, it's not an old connection. I'll like to avoid running Windows on my laptop. I'm giving some plugins for my IDE a whirl, but still no solution for me.
#Matthew Schinckel Navicat seems to only have a non-commercial Oracle product...I need a commercial friendly one (even if it costs money).
I get the same problem after there's been an active connection sitting idle for a while. I solve it by restarting sql developer every once in a while.
I also have Toad for Oracle running on a vmware XP session, and it works great. If you don't mind the money, try that.
The company Navicat has released an Oracle client for Mac (and they do a Windows version too).
It's not free, but I think you can get a 30 day demo.
Have you looked at http://www.aquafold.com/? They have a very JDBC/java Mac-friendly utility, Aqua Data Studio (ADS) that you can try for I think 30 days. It's not free, but...
Excellent support via Yahoo groups. VERY responsive re bugs or enhancement requests.
No affiliation with them - just a fan.
Squirrel is a nice database agonstic application development client. No Oracle specific features, but runs well on the mac
I use SQLDeveloper on the Mac and have had problems where it becomes unresponsive. Usually, I can fix this by going into the Activity Monitor and killing the process. However, this doesn't always work to end the process. When that happens, I go to the Terminal and find the process id and send it a SIGKILL and then the next time it will work correctly.
However, more importantly I evaluated SQLGrinder at one point. I didn't end up buying the software, largely because I have a Mac laptop and a windows desktop. Therefore, I more often use Toad on the windows desktop and it wasn't worth purchasing SQLGrinder for me.
Use RazorSQL. Do yourself a favor and spend the 60 bucks. It will pay for itself in the first hour or two of use. You may even be able to get 60 days for free out of it.
The latest version of SQL Developer is very good and I have experienced no problems with it on my Mac Pro. DB Solo 3 is also quite good.