I'm using Tokyo here at work to develop our software. The rest of our team is still using XE5. Our build is still in XE5. A QA team member came to me and said one of the calculations (Insurance stuff), is taking 42 seconds. She asked me to try it on my machine. Mine takes 2 seconds. So I compiled the EXE and the DLL (with the calculations) on my machine with Tokyo, and she determined it takes 4 seconds (she's running on a virtual machine).

I'm using Tokyo here at work to develop our software. The rest of our team is still using XE5. Our build is still in XE5. A QA team member came to me and said one of the calculations (Insurance stuff), is taking 42 seconds. She asked me to try it on my machine. Mine takes 2 seconds. So I compiled the EXE and the DLL (with the calculations) on my machine with Tokyo, and she determined it takes 4 seconds (she's running on a virtual machine).

I suspect that there are a lot of optimizations that took place between XE5 and Tokyo, but can anyone quantify this? I'm trying to get them to move to Tokyo.

Comments

  1. Edmilson Mattos FinalBuilder, DUnitX and Continua CI saves our bacon on every commit.

    ReplyDelete
  2. We use TeamCity w/ DUnitX and Ranorex+SpecFlow to verify our builds with both unittests and ui tests on each commit.

    ReplyDelete

Post a Comment