Originally posted by Gimbal Since no normal PC can keep up with that rate it's not really fair to call the K-5 slow, unless you call PC's ultra-slow.
It's not exactly a fair comparison, because as far as I know there's no such thing as a minimal, speed-optimized RAW converter written in assembly language. That's what you'd have to use to compare somewhat fairly to in-camera processing
My entire point is that converters on PC can afford to be
much more CPU-intensive, since 1) the power is there and 2) the time is available. A camera has two disadvantages to any modern PC; a slower processor, and less than two-tenths of a second to perform the conversion. Rest assured that your quad-core PC could run rings around the K-5 if it wanted, but there are simply no implementations of that algorithm for that platform that I know of.
EDIT: We're getting into territory where it is impossible to compare embedded hardware intended to do one thing to a general-purpose PC, but let's just ballpark estimate the differences in raw power we have to do with here: the Fujitsu FR80 core in the K10D (which itself is a part of the Fujitsu Milbeaut M-4 MB91680 dedicated image processing chip; no idea what hardware is in the K-7 or K-5) runs at 200 MHz, does 259 MIPS, has 8K cache... So yes, by PC standards, a camera is SLOW. It's very fast at what it does, but write an optimized program for a 64-bit, quad-core Intel-compatible CPU to do the same thing and the FR80 is going to go home and cry in a corner. And before someone asks: no! none of this will help me or you take better pictures, but I am not only a photographer, I am also a computer nerd
Last edited by Erik; 11-26-2010 at 08:15 AM.