Always Test before Mass Update

Sometimes I forget with simple "Service Packs" of any program, that they all should get adequately tested before installing on a mass of computers. So, we have a user that was having serious issues that the rest of their team was not having on a 180mb Revit file. Even though none of this user's issues were on the fix list I had hoped that it would resolve some of the issues until we could get the user a new computer. After installing the Service Pack 2, the user would have Revit close (without warning or error report) when they would attemp a save to central command. I had to do a system restore because there was nothing I could alter on the machine that would allow the program to save to central. Luckily, since we are switching out hardware so that the users will have Vista 64bit with Revit 64, I only installed the Service Pack (Web Update) 2 on one computer.

Just a reminder that you should always test before installing on too many computers. I almost forgot and if we were not changing out hardware I would probably have suggested installing it on 50 computers. That would have been a headache!

This could have been a system issue so I am in no way suggesting that you not use the new Revit update.

Revit 64-Bit Benchmark Results

Before the 64-Bit was even released I was just finishing up a benchmark program that was very difficult and taxing on RAM and processor. We were trying to figure out what laptop would be best for our Revit users. Since the 64-Bit has been released I have now run it and was shocked at the improvement. On another note, I was let down that the SP2 for 2009 was actually slower then the WU1 but that quickly disappeared when I heard about the 64-Bit version. Below are the results:Below is an image from the benchmark. It is way overmodeled with bolts, complex chairs, glass beakers in the shelves in the lab and so forth.