Date: | Tue, 4 Mar 2008 19:23:39 -0800 |
---|---|
From: | "Andreas Sæbjørnsen" <andreas.saebjoernsen@xxxxxxxxx> |
Subject: | [Gems-users] measuring log size |
Hi, I am interested in measuring the maximum simulation log size in LogTM. I notice that TransactionVersionManager has a variable of type int* called m_logSize of size smt_threads. Would the total log size of the LogTM log be equal to the sum of the elements in this array? What is the units of this size? If so, where would you recommend instrumenting the code in order to find the largest total log size during one simulation? I was thinking of adding a member variable m_totalLogSize in the class TransactionVersionManager in 'ruby/log_tm/TransactionVersionManger.*' of type int which stores the current largest log size. The value for the largest log size would be computed in the beginning of void TransactionVersionManager::commitTransaction(int thread, bool isOpen); void TransactionVersionManager::restartTransaction(int thread, int xact_level); and if the computed value is the largest then m_totalLogSize variable is updated (I only expect one instance of the class). Should I expect this to do the trick? I appreciate any comments. thanks, Andreas |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] LogTM SE in Gems 2.1, Jayaram Bobba |
---|---|
Next by Date: | Re: [Gems-users] measuring log size, Jayaram Bobba |
Previous by Thread: | Re: [Gems-users] Machine, Node, MachineID, NodeID, divya ramakrishnan |
Next by Thread: | Re: [Gems-users] measuring log size, Jayaram Bobba |
Indexes: | [Date] [Thread] |