U++ forum: Welcome to the forum

Re: U++ infrastructure server... [message #16770 is a reply to message #16761]

Thu, 10 July 2008 15:07

mirek
Messages: 13976
Registered: November 2005

Ultimate Member

mr_ped wrote on Thu, 10 July 2008 04:56

luzr wrote on Wed, 09 July 2008 22:35

mdelfede wrote on Wed, 09 July 2008 13:31

VmWare can use all processors on a single machine... but I agree that it's not the most important stuff, in particular with a build server. You don't need a lightning speed for building, IMO.

It might be important for unit testing.

Mirek

It's just game of words as the technology is pretty much the same, but you mean automated tests, right?
Because unit tests, if they should be run after each build after every little change, they have to take 2-5seconds at most (I'm usually around 0.1s to 0.5s in my small projects) to not make you sad. Usually I can cover 100% of code with O(1) and O(small N) tests, and any thorough O(n) and more tests I move into automated application tests, which I don't run after every build like Unit tests. Those I run only when I did finish some step of development.

Anyway, if the tests are not written to use multi-core, they will not benefit from it anyway. And the easiest way to use multi-core is to run multiple single core tests at the same time. If we assign each platform single core (and I think you will sooner run out of cores, than out of platforms Smile

), I think the overall performance will be ok. Even if some core will be bored occasionally.

Yep, automated testing.

Anyway, the real point is that we are about to test MT stuff too. Means we need multithreaded tests that really run on multiple cores. Some bugs are revealed only this way.

Mirek

Report message to a moderator