Optimizations

Premature and/or over-optimization is often claimed to be a root of most evil in the programming world. However, what to do when optimization IS necessary?

IT Hares discuss certain not-so-trivial optimization techniques. It doesn’t mean that you should use them at all costs (and most likely, you don’t); however, if you do have a reason to optimize – this information may be handy.

Parallel Coding: From 90x Performance Loss To 2x Improvement

April 4, 2018 by “No Bugs” Bunny

Parallel vs Single-Threaded: Speed vs Power Consumption

Quote:

as long as serial code provides good-enough response times from end-user perspective – DON’T PARALLELIZE

Another Quote:

out of all the premature optimizations, premature parallelization is the most premature one

Filed under: On.ProgrammingTips and TricksOptimizations

Read more

Using Parallel (algorithm) Without a Clue: 90x Performance Loss Instead of 8x Gain

March 27, 2018 by “No Bugs” Bunny

Parallel vs Single-Threaded

Abstract:

I made an experiment which demonstrates Big Fat Dangers(tm) of implying that parallelization can be made as simple as just adding a policy parameter to your std:: call.

Quote:

it is still necessary to understand what we’re doing

Filed under: On.ProgrammingTips and TricksProgramming LanguagesOptimizations

Read more

C++: Thoughts on Dealing with Signed/Unsigned Mismatch

March 6, 2018 by “No Bugs” Bunny

-1 ></a> 0U

Quote:

we’re just narrowly avoiding a disaster without understanding how close we were

Another Quote:

there is a chance that intuitive::lt MIGHT be a good thing to make behaviour of our C++ code to correspond better to our-expectations-when-we’re-reading-it

Filed under: On.ProgrammingTips and TricksProgramming LanguagesOptimizations

Tagged With: C/C++GCC/Clang
Read more

OLTP Database Optimization 102 – DIY Heterogeneous Replication (Part II)

October 31, 2017 by “No Bugs” Bunny

DB Replicas

Quote:

The point of Super-Replica is that it is a replica Slave DB which is larger than original Master DB

Another Quote:

this “don’t write some HISTORICAL data to Master DB” approach can easily allow to reduce the load on the Master OLTP DB by a factor of 2x-3x

Filed under: Book: D&D of MOGs1st beta of Vol. VII-IXOn.ProgrammingOptimizations

Read more