enable disk cache policy for x3650 M3 ServeRaid Adapter M1015

I have to setup two new IBM x3650 M3 machines with 10 SAS drives and the built in ServeRaid M1015 adapted (manufactured by LSI AFAIK). Using the MegaRAID Storage Manager 6.90.0600 that I've downloaded from the IBM website I can setup a RAID 10 with 6 disks just fine (RAID 10 with four disks I've setup for the Windows 2008 R2 OS).
By default the MegaRAID software downloaded from IBM sets Access Policy = Read Write, Disk Cache Policy = Disable, Read Policy = No Read Ahead. Write Policy-IO Policy=Direct IO, Current Write Policy=Write Through and Default Write Policy=Write Through. All parameters can be changed but offer no other options as the one mentioned, except "Disk Cache Policy" can be set to "enabled".

The M1015 does not have a BBU so I guess this is the reason why the only option for example for Write Policy is "Write Through".

However I am wondering whether it is o.k. to set Disk Cace Policy to enabled ? WIth Disk Cache policy disabled I have around 120 MB/s seq write speed (tested with Diskmark) and with Cache policy enabled I have around 350 MB/s. (Read speed is 420 MB/s)

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Is it OK?    Sure, if you don't mind the extra risk of data loss in event of a controller failure, certain types of drive failures, power failure, or a BSOD.   If you feel lucky, have a UPS, and back up often, go for it.
PeterSausDAuthor Commented:
dlethe, are you considering that the write policy setting is still "Write Through" when you wrote your comment ? Do you know exactly what the "enable" disk cache mean for this controller ?
The HDDs themselves each have their own write cache.  This is independent of the controller's write cache which is used to queue up and reorganize write requests.  
The current settings are the fastest option to get the data on the disk from the controller even if they are not the fastest overall throughput. Enabling the cache on the controller inserts a delay as the controller manages the write requests. If that cache is not backed up, which it is not without a BBU on the controller, then you are increasing the risk of data loss.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Hardware

From novice to tech pro — start learning today.