A millisecond is too fat

A millisecond is too fat

Today's computers are reaching upwards of 6Ghz speeds, but the system clock hasn't changed muchsince the first 8086. I'm a software developer. I'm hitting this problem. The smallest unit of time I have to work with is the tick of the system clock, ie; 1 millisecond. If I run a routine in a loop that starts with a random number, that loop can start over before 1 millisecond ticks to the next.

There's this thing with computers that if you seed the random number generator with the same number. I run an apwith a routinethat starts with a random number (which gets generated bythe clock)and performs over 1,000 calculations based on random sampling. I get two, three, even up to five results repeating before new results show.. then the same repeating again.

Amillisecond is too fat. We need a new clock with skinnier time slices.

publicaciones de 4 / 0 nuevos
Último envío
Para obtener información más completa sobre las optimizaciones del compilador, consulte nuestro Aviso de optimización.