Pitfalls of Performance Testing
Beware the casual performance test, it will lie to you. It is simple to write something that gives you timings, but it is difficult to
Beware the casual performance test, it will lie to you. It is simple to write something that gives you timings, but it is difficult to
Asking questions about performance online universally invites scorn and accusation. A large number of programmers apparently feel that the efficiency of code is nowadays insignificant.
In the article on “How Polymorphism Works: Part 1” we learned how to create virtual functions. The method which we chose has at one significant
Polymorphism: the core of object oriented programming. Most modern languages have some concept of interfaces, virtual functions, and classes. Though each language differs in details,
We all know that operations in a computer happen one after the other. Having multiple CPUs and instruction reordering tends to obfuscate the issue. Technically
We’ve all heard that a CPU may reorder access to memory. Yet if you’ve looked further you’d also see that cache coherence ensures the memory
Multi-threaded programming calls for semaphores, synchronized blocks, mutexes, or whatever your language happens to call them. Most of us basically understand why we need them:
In the grand scheme of execution costs function calls come very close to the bottom of the list. They don’t cost very much at all
Whether C++, Java or any other language, we are all familiar with instantiating an object. In those aforementioned languages the operator new happens to do
As high level languages become more abstract, and offer more convenience features, it is easy to lose track of what the computer is actually doing.
Signup to my mailing list to get notified of each article I publish.
Made with Elementor. Hosted with SiteGround. Domain from Netim.