Optimize filesystem for speed over integrity
Going with the default filesystem on a OS X/macOS install
The man page for mount on macOS lists only two options that are performance related to hfsplus:

 - async         All I/O to the file system should be done asynchronously.
                 This can be somewhat dangerous with respect to losing
                 data when faced with system crashes and power outages.
                 This is also the default.  It can be avoided with the
                 noasync option. 

- noatime        Do not update the file access time when reading from a
                 file.  This option is useful on file systems where there
                 are large numbers of files and performance is more criti-
                 cal than updating the file access time (which is rarely
                 ever important).


So, only the noatime option is left to further improve on the default behaviour.
Since there is no fstab on macOS you have to (re-)mount your filesystems in another way.
The most popular search engine hit to achieve an automatic re-mount lists this method:
Create a file called com.noatime.plist in /Library/LaunchDaemons. If you only have 1 SSD partition – that is where your OS is booting from – this is all you need.
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&gt;
&lt;plist version=&quot;1.0&quot;&gt;
    &lt;dict&gt;
        &lt;key&gt;Label&lt;/key&gt;
        &lt;string&gt;com.noatime.root&lt;/string&gt;
        &lt;key&gt;ProgramArguments&lt;/key&gt;
        &lt;array&gt;
            &lt;string&gt;/sbin/mount&lt;/string&gt;
            &lt;string&gt;-vuwo&lt;/string&gt;
            &lt;string&gt;noatime&lt;/string&gt;
            &lt;string&gt;/&lt;/string&gt;
        &lt;/array&gt;
        &lt;key&gt;RunAtLoad&lt;/key&gt;
        &lt;true/&gt;
    &lt;/dict&gt;
&lt;/plist&gt;

Set the ownership of the file with the command
sudo chown root:wheel /Library/LaunchDaemons/com.noatime.plist
sudo chmod 644 /Library/LaunchDaemons/com.noatime.plist

Restart the system or
sudo launchctl load -w /Library/LaunchDaemons/com.noatime.root.plist
To verify, enter the command mount at a Terminal prompt. You should see noatime listed as an attribute of your filesystem.
But what does it do? Well, simply put: it executes this command at boot time (well, after boot, during the load sequence for the rest)
mount -vuwo noatime /

I’m assuming you have a clue what the “mount” command does, but look at the options:
-v     = verbose; actually… this is not absolutely required since it’s a headless command above; although presumably it might show up in the system log somewhere and in cases of failure
-u  the -u flag indicates that the status of an already mounted file system should be changed. (By this point in the load sequence our filesystems have already been mounted)
-w  mount the file system read-write - probably not 100% needed)
-o noatime (Set the noatime option)
Going with alternate filesystem options altogether
Apple filesystems are quite bad from the start  and support for alternative filesystems is also lacking. But that does not  mean you are completely out of options.

You might go for RAM-Disks
You could try to use alternative filesystems like ZFS or another filesystem to your liking via fuse.
You might try and use the as of Sierra, hm, 'usable' new filesystem AFPS (strongest caveats: is beta still and will behave like one for months to come)
You might be a conservative blockhead and sacrifice overhead things like journaling or corestorage volumes with encryptions (that would be otherwise not recommended, but considering your special needs…). Alas, these are not mount options but need you to provide partitions in that style. (And while the mount option noatime might be applied there also, I do not have benchmarks ready to compare on a modern Sierra system running unjournaled filesystems vs the defaults.)