3 ms·
Well, for a ballpark figure: md5sum of 3.4 kernel.tar.gz (average of three runs) 512Mb Slicehost 2.2Ghz Quad-Core AMD Opteron(tm) Processor 2374 HE = 0.275 se
by rythie 14y ago
Well, for a ballpark figure:
md5sum of 3.4 kernel.tar.gz (average of three runs)
512Mb Slicehost 2.2Ghz Quad-Core AMD Opteron(tm) Processor 2374 HE
= 0.275 seconds
512Mb BeagleBoard XM 1GHz Cortex A8
= 2.023 seconds
- argus 14y agowhere was the file stored on the beagle? that could explain a good part of the difference in results you're getting.
- rythie 14y agotime dd if=linux-3.4.tar.bz2 of=/dev/null is 0.7 seconds on the beagleboard and slicehost is more variable but comes to down to 0.5 seconds after a few goes from (1 second). I'd expect it to be read from the page cache anyway. However, I remembered that the beagleboard is using busybox and really the systems are very different from each other, different distribution for example. Update: busybox md5sum is about 20% slower than regular md5sum.