Debugging, no molasses

I discovered the secret to getting Eclipse debugging to not be painfully slow. The secret is to reboot (or possibly just log off and on again) and then make sure you don’t start IE or Outlook or anything else except Oracle, jboss and the app. At that point I’m using just a hair over 2Gb of memory and it’s hardly swapping at all.

I’m sure it would be a huge violation of their security policies, but I’d love to bring in my laptop to see how of does at this. Not only does it have a faster processor and twice as much ram, but it also would allow me to have only Oracle, jboss and the app running on the desktop box while Eclipse ran on the laptop, freeing up half a gig of ram on the desktop.

5 thoughts on “Debugging, no molasses”

  1. Good lord, they’ve got you running your own development database on your own desktop like an animal.

  2. Paul, yeah, but think of all your own hair you won’t have to pull out while waiting for the silly thing.

  3. Don’t have any hair to pull. Hey, if they want the bug fix to take 6 days instead of 3, that’s their problem, not mine. Unlike previous jobs, I’m trying very hard not to get invested in the results, because that way madness lies.

Comments are closed.