How to measure the RAM read/write performance
From: sandeep kumar <hidden>
Date: 2013-02-27 10:08:00
"volatile" only say to the compiler to not put the variable in a register. Could i ask why does you want to mesure the speed of the RAM ? Is it to
study the NUMA behavior of the machine? In development phase of the board, we are trying to measure RAM performance gain while changing type of the RAM. The standard benchmark tools are giving us the Cache performance only. So we want to try some method to measure RAM performance. On Wed, Feb 27, 2013 at 2:30 PM, Karaoui mohamed lamine [off-list ref]wrote:
2013/2/27 sandeep kumar [off-list ref]quoted
quoted
quoted
I am not sure but what if you make the variable as a volatile?Hey i tried. But still is showing the same time for int & volatile int."volatile" only say to the compiler to not put the variable in a register. Could i ask why does you want to mesure the speed of the RAM ? Is it to study the NUMA behavior of the machine?quoted
Thanks Sandeep On Tue, Feb 26, 2013 at 6:50 PM, ankur dwivedi [off-list ref]wrote:quoted
I am not sure but what if you make the variable as a volatile? On Tue, Feb 26, 2013 at 5:01 PM, sandeep kumar < coolsandyforyou at gmail.com> wrote:quoted
Hi All In performance benchmark tools, When we profile read/write timings mostly, those read/writes are done to cache only. I want to measure my DDR(RAM chip) performance. So i want to make sure, every read/write should happen to DDR RAM chip only. How can i achieve this...Any ideas/suggestions...? -- With regards, Sandeep Kumar Anantapalli, _______________________________________________ Kernelnewbies mailing list Kernelnewbies at kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies-- Thanks Ankur Dwivedi-- With regards, Sandeep Kumar Anantapalli, _______________________________________________ Kernelnewbies mailing list Kernelnewbies at kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- With regards, Sandeep Kumar Anantapalli, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130227/f713c7ed/attachment.html