Edgewall Software

Changes between Initial Version and Version 6 of Ticket #519


Ignore:
Timestamp:
Apr 28, 2010, 12:40:49 PM (14 years ago)
Author:
dfraser
Comment:

OK, but I'll target it to the next milestone... clarifying in the summary and description too

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #519

    • Property Status changed from new to reopened
    • Property Operating System changed from Windows to
    • Property Component changed from Build master to Administration interface
    • Property Summary changed from huge database cannot be cut down again to Allow deletion of old logs through web interface
    • Property Priority changed from major to minor
    • Property Milestone changed from 0.6 to 0.7

  • Ticket #519 – Description

    initial v6  
    1 I use the svn version of bitten with Apache 2.4 and trac 0.10.4 on a Windows Server 2003 RC2 SP 1.
     1Original report:
     2> I use the svn version of bitten with Apache 2.4 and trac 0.10.4 on a Windows Server 2003 RC2 SP 1.
     3> Over month many builds have produced a huge database of 1,85 GB. The build system runs about 10 platforms in parallel. We have committed about 3000 revisions over the past 12 months. Each build consists of 5 steps, each one with a complete command-line output of the compiler+linker we run.
     4> It seems trac stores all the logging of the builds in its project database and as we reached a size nearly of 2 GB, the whole server system becomes slow and even Apache crashes from time to time.
     5> I want to cut down the database and free it from the ancient build logging, but I've found no way to do so. The database size remains the same although I set a new (much higher) start revision in the admin web page of the bitten build configuration. I expected the database to reduce its size but it has not happen.
     6> Don't know what to do now. Seems it's not supported (?)
     7As of the 0.6 release series, the log files are now stored on the file system, which reduces the size of the actual database file.
    28
    3 Over month many builds have produced a huge database of 1,85 GB. The build system runs about 10 platforms in parallel. We have committed about 3000 revisions over the past 12 months. Each build consists of 5 steps, each one with a complete command-line output of the compiler+linker we run.
    4 
    5 It seems trac stores all the logging of the builds in its project database and as we reached a size nearly of 2 GB, the whole server system becomes slow and even Apache crashes from time to time.
    6 
    7 I want to cut down the database and free it from the ancient build logging, but I've found no way to do so. The database size remains the same although I set a new (much higher) start revision in the admin web page of the bitten build configuration. I expected the database to reduce its size but it has not happen.
    8 
    9 Don't know what to do now. Seems it's not supported (?)
     9This ticket is now being used as a request to be able to remove old log entries and files (hopefully through the web interface)