Switch to using setOnInsert about cobra HOT 3 CLOSED

Performance is actually not as good:

• every request is now larger and takes longer to process
• versus having 1 failed update an hour and 1 required insert, and then 1 final update: 2 extra (3 total) requests per hour

from cobra.

• The top results are using setOnInsert and averaging around 20 or less.
  • Also notice the increase netIn and locked db! Wow!
• The lower (more recent) results are using the original method with a failing update and an insert then retry update request. It successfully reaches 100 updates per second, easy.

from cobra.

Implemented on branch https://github.com/Glavin001/Cobra/tree/setOnInsert

from cobra.