Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
08/02/06 21:55
Read: times


 
#121598 - CPU Overhead
Responding to: ???'s previous message
Erik Malund said:

The 'overhead' I have most trouble with is TIME.


Ok yes, that is always an overhead. I think though, the issue was speed vs overhead. Overhead being: (my definition)

A) Code size/space (ROM)
B) Variable usage/space (RAM all variations)


you can not state that one factor is 'overhead' that, again, is application dependent.

You can write a function/subroutine in, say, 53 bytes of code or in 5 bytes of code and 256 bytes of table in code memory, which of the two is 'overhead' is application dependent.

Erik



Yes, application dependent. The question is what are you optimizing for... speed or size (resource overhead) or both. No it's not a one size fits all type of thing, not all situations are going to be the same.

I've been doing some searching here and have started compliling some of the ideas, programming practices, techniques, etc. to either reduce time required or to reduce ROM/RAM overhead. I still think it could make a good FAQ. Due to my limited (almost none) experience with C, I'll have to go with what I can find here. I know it is a very broad subject and will have to be generalized, but I think it is worthwhile.

Jon

List of 33 messages in thread
TopicAuthorDate
code optimisation            01/01/70 00:00      
   Optimisations            01/01/70 00:00      
   problem solved            01/01/70 00:00      
      good closure!            01/01/70 00:00      
         and the very best ...            01/01/70 00:00      
            Isn't that why we have "tools"?            01/01/70 00:00      
               not quite and a good read            01/01/70 00:00      
               A Posidriv driver and a Phillips screw            01/01/70 00:00      
                  I have done this too, I think you are wrong            01/01/70 00:00      
                     Best Ways?            01/01/70 00:00      
                        what is best?            01/01/70 00:00      
                           Guide lines and trade-off\'s            01/01/70 00:00      
                              what about 'and'            01/01/70 00:00      
                                 Dangerous Information            01/01/70 00:00      
                                    depends on what you define as overhead            01/01/70 00:00      
                                       Overhead            01/01/70 00:00      
                                          the whole truth, please            01/01/70 00:00      
                                             one good thing...            01/01/70 00:00      
                                             CPU Overhead            01/01/70 00:00      
                                                there is an article 'somewhere' that cover C for            01/01/70 00:00      
                                                   the real optimum            01/01/70 00:00      
                                                      Your time is appreciated            01/01/70 00:00      
                                                   how about these?            01/01/70 00:00      
                                                      a required capability for optimum code            01/01/70 00:00      
                        small and readable            01/01/70 00:00      
                           my sentiment            01/01/70 00:00      
                              In that spirit ... where's the user guide?            01/01/70 00:00      
                                 Did you download the documentation            01/01/70 00:00      
                                    have a look            01/01/70 00:00      
                                       Non-GPL            01/01/70 00:00      
                                       I'll have a look!            01/01/70 00:00      
                                    It's not quite as the page suggests            01/01/70 00:00      
                        Lint            01/01/70 00:00      

Back to Subject List