I was trying to say: "consider the abstractions, and make them more leaky when necessary" (e.g. allow a flag to say "don't do the expensive calculation"), not "remove the abstractions".
The traditional BLL/BOL/DAL architecture is probably the worst. It aims for some kind of fantasy "separation of concerns" between the business layer and the data access layer, but many concerns simply can't be classified as exclusively business concerns or exclusively data access concerns. When people attempt to introduce and enforce such a separation, they end up with all sorts of performance problems.
It can be looked at on a few levels.
One is the "simple things" that waste a few seconds here and a few seconds there and pretty soon we are talking about hours.
Another is the algorithm that does more work than it has to do, scales poorly, etc.
In my mind "encapsulation" and "abstraction" do tend to be leaky when it comes to things like: performance, security, thread safety, scalability, etc.
In C++, `unique_ptr` is an "abstraction layer" with no runtime overhead, that will probably make your code faster due to the better safety.