If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

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 neccessary?

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.

Optimizations, page 2:

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

posted by

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”
[→]

OLTP Optimization 102: DYI Heterogeneous Replication. Part I (Basics)

posted by

Quote: “there are still several Big Fat ReasonsTM to use DIY replicas”
Another Quote: “With the Replication Messages described above, it is ok to apply Replication Messages to Slave DB which is newer than exactly necessary.”
[→]

OLTP DB Optimizations 102 – Group Commits

posted by

Quote: “if we can commit several transactions at the same time – RDBMS needs to fsync() our DB logs to physical disks only once”
Another Quote: “if going our preferred way of single-writing-DB connection – make sure NOT to use RDBMS-level Group Commit”
[→]

OLTP DB Optimizations 102 –100% Coherent App-Level Cache for Single-writing-DB-connection

posted by

Quote: “with our app-level cache, we’re guaranteed to get exactly the same results as if we’d be querying the underlying database.”
Another Quote: “why settle for invalidation when we can modify cache accordingly, saving on the extra DB request when we’re dealing with the same USER again?”
[→]

Allocator for (Re)Actors with Optional Kinda-Safety and Relocation

posted by

Quote: “‘Safe with relocation’ mode will allow us to eliminate dreaded ‘external fragmentation’ – which tends to cause quite a bit of trouble for long-running systems”
Another Quote: “For a long while, I have been a strong proponent of message-passing mechanisms over mutex-based thread sync for concurrency purposes”
[→]

Ultra-fast Serialization of C++ Objects

posted by

Quote: “in both these cases we can be 100% sure that we’ll be deserializing this state on the executable which is identical to the executable which serialized the state.”
Another Quote: “Even when comparing with home-grown code with per-field serialization, our Ultra-Fast Serialization still wins (up to 1.5x-2x) “
[→]
Copyright © 2014-2016 ITHare.com