Hi Kiste, > Oh well, you got me bending the truth ;-) In fact, the highest number i've > measured was about 520kByte/s. That was using a modified read_sector(), that > did not use large_array and had the 100ns delay completely missing. One of my > hard drives in test can work without that delay at 32MHz.
That's realy fast and also means you fill up all memory in 2ms. And then you have to actually do something with this data. Years ago I read a chapter on optimisation in the book 'programming pearls' of Jon Bently. The major message was: look at the big picture, or you'd optimise the wrong issues. For us, library developers, it's not possible to anticipate on each application, we can imagine an average app with our libraries and optimise for efficent resource use (ram, flash and speed). Tschüss Joep -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
