[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 655] New - add "operation count" to trails
From:       issues () subversion ! tigris ! org
Date:       2002-03-12 23:08:12
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=655

*** shadow/issues_15/655	Tue Mar 12 15:08:12 2002
--- shadow/issues_15/655.tmp.16896	Tue Mar 12 15:08:12 2002
***************
*** 0 ****
--- 1,30 ----
+ +============================================================================+
+ | add "operation count" to trails                                            |
+ +----------------------------------------------------------------------------+
+ |      Issue #: 655                       Component: subversion              |
+ |       Status: NEW                         Version: current                 |
+ |   Resolution:                            Platform: All                     |
+ |   Issue type: ENHANCEMENT              OS/Version: All                     |
+ |     Priority: P3                     Subcomponent: src                     |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: issues@subversion.tigris.org                                 |
+ |  Reported By: gstein@tigris.org                                            |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |    Milestone: TargetMilestone: ---                                         |
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ It would be good to see how many database operations we perform within a single
+ trail. If that number is O(N), then it means that we are holding a lock for an
+ N-bounded period of time, which could be bad. This is especially bad if the
+ number of operations is larger, per N.
+ 
+ As a diagnostic to figure out if/where we are holding a trail open for too many
+ operations, we should add an "op_count" field to the trail structure, and
+ increment it for each database operation performed within that trail. (and then
+ somehow, dump out that info as appropriate)
+ 
+ If we find trails with more than, say, a dozen operations in them, then we have
+ candidates for breaking an operation into smaller component parts which hold DB
+ locks for shorter periods of time.
\ No newline at end of file

[prev in list] [next in list] [prev in thread] [next in thread]