Skip to main content

Speed up Eclipse from a slow workspace

After working on a few Java/JEE projects, your workspace really gets to become fat. I mean, it gets very very slow. This is because you opened and closed a lot of projects with a loooot of resources in it.

Also because every time you press that Ctrl+Shift+R, or Ctrl+Shift+O, or Ctrl+T in java or run some free text search, You are loading up eclipse's cache of index. Also JDT slowly keeps a track of it, for Type Hierarchies, Implementations.

The easiest way is to open a workspace for every unrelated project. Keep it small. But sometimes, it is not possible. Dependencies. Ease to work with one monolithic workspace (opening and closing projects - yea that's me). For these cases, You could just clean up the .metadata\.plugins\org.eclipse.jdt.core folder in your workspace.

If you are feeling even lucky, go ahead, clean up .metadata\.plugins\org.eclipse.core.resources\.history... a. a. aa. Wait, That folder, contains all that local history of files you have changed - LOCALLY (NOT cvs or svn history). So if you are working on some files without committing them in and rely on the local history to go back, Do not do this step.
Labels:

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery
Read More >>

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...
Read More >>

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...
Read More >>