Tuesday, April 1, 2008

Chronicles of a Visual Studio user

Performance has always been the weakness of Java IDEs.

Far be it from M$ to be left behind in the poor performance shootout.

Every now and again VSS decides it needs to stop responding. This seems to be while you debug stuff.

It just seems to randomly deadlock.

Here is the sad story in the task manager:

A few points worth noting:

  • Look ma, no cpu usage.

  • 486Mb memory usage on a natively compiled application.

  • At this point in time the actual memory exceeds the virtual memory allocated to VSS by windows.

  • VSS is using more memory than my MSSQLServer installation.
  • No comments: