Limits on RamDisk w/ SQL?
Posted: Tue Nov 07, 2017 4:18 pm
We are currently using your Primo Ramdisk Server Edition (v5.7.0) on the following machine..
- Role: MS SQL 2016 Standard with SP1
- Total server ram 384gb DDR4 2400
- CPU Intel Xeon E5-2697A v4 16core
We have been encountering an issue with an instance of SQL server running on the box that…
- Uses its “TempDB” stored on a Ramdisk made by your product
- In that the entire instance gets “stuck” on a single 8k page of TempDB
- And in turn brings the entire instance to a crawl / halt for seconds (minutes at times)
- And in turn causes issues w/ our platform.
We’ve been using PrimoRamdisk for some time now w/ out issue or occurrence of this, and we are wondering…
- Is there some type of “limit” to the iOPS that can go through your software’s ramdisk?
- Is there a windows perfmon counter we can watch to see if this is the case?
- Are there any special settings or “tricks” that you can pass along for best configuring your product to work w/ MS SQL?
o Any changes we should make to MS SQL server itself to work with your product better?
o I’ve attached a zip file containing the disk descriptor for this server
- Could this be caused by CPU pressure?
o If the server was at 100% CPU, is it possible it’s not going to be able to work with your RAMDISK correctly?
Any help would be greatly appreciated!
- Role: MS SQL 2016 Standard with SP1
- Total server ram 384gb DDR4 2400
- CPU Intel Xeon E5-2697A v4 16core
We have been encountering an issue with an instance of SQL server running on the box that…
- Uses its “TempDB” stored on a Ramdisk made by your product
- In that the entire instance gets “stuck” on a single 8k page of TempDB
- And in turn brings the entire instance to a crawl / halt for seconds (minutes at times)
- And in turn causes issues w/ our platform.
We’ve been using PrimoRamdisk for some time now w/ out issue or occurrence of this, and we are wondering…
- Is there some type of “limit” to the iOPS that can go through your software’s ramdisk?
- Is there a windows perfmon counter we can watch to see if this is the case?
- Are there any special settings or “tricks” that you can pass along for best configuring your product to work w/ MS SQL?
o Any changes we should make to MS SQL server itself to work with your product better?
o I’ve attached a zip file containing the disk descriptor for this server
- Could this be caused by CPU pressure?
o If the server was at 100% CPU, is it possible it’s not going to be able to work with your RAMDISK correctly?
Any help would be greatly appreciated!