This has some overhead, data is first written to memory (not yet acknowledged) then flushed to disk, only then acknowledged.
So it does not allow faster write completion, rather possibly slightly slower as other cache data may need to get evicted for the new to have space. Normally only makes sense if your clients need to read the data directly after the write and that more than one time. This is not a regular pattern, as read caching is most of the time done by the clients them self, as they know better what specific data may have a bigger chance to get re-read.
We recommend in general against enabling this, and if you probably have a non-normal access pattern and should try to evaluate the impact of this change first in a non-production setup for your specific access patterns.