jefrado
Mechanical
- Jun 9, 2006
- 44
I have a macro that basically takes an assembly with lots of subassys and parts and up dates it with what we need via inputs from excell. The macro basically updates all assemblys and parts by configuration in some cases and design tables in others, then renames everything and throws it into a unique directory.
I was able to get a new machine and loaded it with 2009 fresh and I got one of those $400 HP laptops that Best Buy had a few weeks ago and loaded it with it too (home license).
Here I found out SW doesn't like recursives. I had to rewrite the macro to get rid of the main recursive (it finds and updates all assemblies) - it crashed every time. When I rewrote it to get rid of this recursive, it fixed it. Funny thing was is that 2008 ran faster with the rewrite also.
The new machine ran a test macro in 2:30 min, my laptop in 2:42 with the existing machines taking 5 to 8 min.
Great, so we loaded 2009 in our other machines. 2009 runs the test macro 15% to 20% slower across the board with the exception of our newest (about 2 yrs old) existing machine which crashes (something about photoworks getting into the mix somehow). I loaded 2008 in the new machine and it runs the macro in 2:30 and lengthened the 2009 time to 3:00.
It looks like a clean install will speed everyone up. What I don't know is whether to stick with 2008. Assuming the relative speed is not going to change with clean installs, it looks like things will run faster in 2008. The only justification for upgrading would then be stability which we cannot test - by the time we found out we would be committed.
Anyone got any bright ideas? Is 2009 any more stable. I am having trouble believing that 2009 is actually not slower.
Thanks
John
I was able to get a new machine and loaded it with 2009 fresh and I got one of those $400 HP laptops that Best Buy had a few weeks ago and loaded it with it too (home license).
Here I found out SW doesn't like recursives. I had to rewrite the macro to get rid of the main recursive (it finds and updates all assemblies) - it crashed every time. When I rewrote it to get rid of this recursive, it fixed it. Funny thing was is that 2008 ran faster with the rewrite also.
The new machine ran a test macro in 2:30 min, my laptop in 2:42 with the existing machines taking 5 to 8 min.
Great, so we loaded 2009 in our other machines. 2009 runs the test macro 15% to 20% slower across the board with the exception of our newest (about 2 yrs old) existing machine which crashes (something about photoworks getting into the mix somehow). I loaded 2008 in the new machine and it runs the macro in 2:30 and lengthened the 2009 time to 3:00.
It looks like a clean install will speed everyone up. What I don't know is whether to stick with 2008. Assuming the relative speed is not going to change with clean installs, it looks like things will run faster in 2008. The only justification for upgrading would then be stability which we cannot test - by the time we found out we would be committed.
Anyone got any bright ideas? Is 2009 any more stable. I am having trouble believing that 2009 is actually not slower.
Thanks
John