Re: [Gems-users] measuring log size

[Jayaram Bobba <bobba@xxxxxxxxxxx>]

Yes.

Andreas Sæbjørnsen wrote:
> When I get the output
>    xact_log_size_dist: [binsize: 64 max: 1632 count: 100000 average: 
> 119.558 | standard deviation: 157.47 | 0 80080 422 15833 0 0 0 0 0 0 0 
> 35 1349 1678 537 0 0 0 0 0 0 0 2 23 39 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
> 0 0 0 0 0 0 0 0 ]
> does that mean that max log size was 1632 bytes?
>
> thanks,
> Andreas
>
> On Tue, Mar 4, 2008 at 7:29 PM, Jayaram Bobba <bobba@xxxxxxxxxxx 
> <mailto:bobba@xxxxxxxxxxx>> wrote:
>     Look for "xact_log_size_dist:" in the ruby stats file. That should
>     give
>     statistics about the log sizes (in bytes) for the transactional
>     program,
>     including the max log size.
>
>     Jayaram
>
>     Andreas Sæbjørnsen wrote:
>     > 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
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Gems-users mailing list
>     > Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
>     > https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>     > Use Google to search the GEMS Users mailing list by adding
>     "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>     >
>     >
>     _______________________________________________
>     Gems-users mailing list
>     Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
>     https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>     Use Google to search the GEMS Users mailing list by adding
>     "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>