There is no guarantee that a solution exists in a 'getwork' data unit.
Better to rename "efficiency" as "luck." It is more clear.
It's "efficiency" in the sense that it's the percentage of how close you are to a 1:1 ratio of getworks asked to answers submitted. It's more "efficient" in regards to a pool because it causes less traffic on the server, and allows for more users to connect and participate, thus increasing the potential for blocks to be solved at a faster rate.
The miner itself yields results at the same speed as the core version of m0mchill's miner, but with a greatly reduced network load.
ef·fi·cien·cy [ih-fish-uhn-see]
–noun, plural -cies.
1) the ratio of the work done or energy developed by a machine, engine, etc., to the energy supplied to it, usually expressed as a percentage.
By dictionary definition, our miner fork is more efficient if you're looking at the getworks as "energy" and answers as "work done".