Is it a good idea to turn off oplocks?
Turning off oplocks is likely to make your application slower, not faster.
Not always. oplocks are great if the data is only used by one client, or is read mostly, or write by one client and read by all others. However, if the data is mixed read-write you get "oplock ping-pong". Client A grabs the oplock, does its stuff and holds the oplock. Client B wants the file, so has to go through an oplock request and oplock break cycle, and wait for Client A to flush the data back to the server. It then gets the oplock and caches the data. Now Client C (or even Client A) comes along...
Oplocks should be off for data files which are likely to be written concurrently by multiple clients, such as shared database files.