Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.kge.msu.ru/workgroups/compcenter/dmitri/projects/rmma/index.htm
Дата изменения: Sat Jun 26 11:57:18 2004
Дата индексирования: Mon Oct 1 21:25:01 2012
Кодировка:
RightMark Memory Analyzer

RightMark Memory Analyzer

Downloads

RMMA v3.2 RELEASE binary (806KB WinRAR Archive)
RMMA v3.1 RELEASE binary (753KB WinRAR Archive)
RMMA v3.0 RELEASE binary (740KB WinRAR Archive)
RMMA v2.5 RELEASE binary (387KB WinRAR Archive)
RMMA v2.4 RELEASE binary (366KB WinRAR Archive)
NOTE: These version should run on any WinNT-based platform. Both standard memory allocation
and AWE are implemented. See the note below on how to enable access privileges for AWE.

RMMA v2.3 binary (366KB WinRAR Archive)
RMMA v2.2b binary (365KB WinRAR Archive)
RMMA v2.1f binary (344KB WinRAR Archive)
RMMA v2.0c binary (304KB WinRAR Archive)
RMMA v1.9 binary (295KB WinRAR Archive)
RMMA v1.8beta binary (290KB WinRAR Archive)
RMMA v1.7beta binary (291KB WinRAR Archive)
RMMA v1.6a binary (288KB WinRAR Archive)
RMMA v1.5a binary (283KB WinRAR Archive)
NOTE: These versions use the AWE extensions available only on Windows 2000, Windows XP and Windows 2003 Server.
They WILL NOT run by default, as they need some user privileges that are NOT enabled by default.

To solve this problem, please follow these steps:
1. Make sure you're logged on with administrative privileges.
2. Go to the Local Security Policy (located in the Administrative Tools folder).
3. Choose Local Policies->User Rights Assignment.
4. Add your user name (or group name, e.g., Administrators) to the Lock pages in memory policy.
5. Log off and log on to the system again. The test should run fine now.

RMMA v1.5 binary (282KB WinRAR Archive)
NOTE: This version should run on any WinNT-based platform.

Known bugs

The cache associativity test (the one obtained from the dependence of cache
latency on the chains count) fails at times (i.e., displays wrong results on L2 associativity).
The reason for this is currently unknown. Re-launching the executable and running the test again,
however, always solves the problem.
UPDATE: This bug hasn't been confirmed in the release versions 2.1 and later.

Resources

Athlon XP cache latency study (somewhat outdated)

Back to the Developments page.