C++ Operator Overloading, and why it blows chunks
To add to what null_pointer said, if you inline functions too much, they obviously take up more space in memory. That increased space increases the likelihood of you overflowing the cache, which is going to incur a performance hit. Whereas if you''d just used a single instance of that function, the code would probably be still cached across subsequent calls. Of course, this is starting to get too low level to worry about at the start, but the general idea is that inlining anything more than a line or 2 long is perhaps counterproductive.
Yup, I know...
I''ve ironed out the huge performance hit from my original vector class, and now I''m simply finishing the entire application before having a second look at what''s slow, and how to make it faster.
Should be interesting to see how much I can squeeze out of it later
#pragma DWIM // Do What I Mean!
~ Mad Keith ~
I''ve ironed out the huge performance hit from my original vector class, and now I''m simply finishing the entire application before having a second look at what''s slow, and how to make it faster.
Should be interesting to see how much I can squeeze out of it later
#pragma DWIM // Do What I Mean!
~ Mad Keith ~
It's only funny 'till someone gets hurt.And then it's just hilarious.Unless it's you.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement