Standup – 22 October, 2009
- A lot of us have been seeing significant slowdown and memory problems with RubyMine lately. One of the Pivots brought this up again today, and remarked that RubyMine performed much better after he removed/detached a bunch of gems and only added back in the ones he was concerned about ever having to go into again.
- Still in the vein of RubyMine, my Pair and I at one point set the memory allocation for RubyMine higher than the initial settings a weeks or so ago. I got to talking with a few of the Pivots about RubyMine and its memory settings and they said this is actually what you do NOT want to do. Apparently if RubyMine has too much memory available, then it doesn’t garbage collect anywhere near as often as it probably should.
- In an Rspec test file, integrate_views is set up to be active by default. However, we want to run a particular describe block in the file in isolation mode. We tried using ‘integrate_views( false )’ right after the describe header, but that didn’t seem to do anything like what was expected. Just calling ‘integrate_views’ when the default is Isolation mode runs a describe block in Integration mode, but is there a way to do the opposite?