--- 
ticket_changes_001: 
  author: Me
  approved: true
  id: 1
  ticket_id: 1
  spam: false
  content: The issue is not that serious
  email: 
  created_at: 2000-01-02 21:30:00
ticket_changes_002: 
  author: Me
  approved: true
  id: 2
  changes: |
    --- 
    Priority: 
      :old: Major
      :new: Minor
  ticket_id: 1
  spam: false
  content: 
  created_at: 2000-01-03 21:30:00
ticket_changes_003: 
  author: Agent
  approved: true
  id: 3
  changes: |
    --- 
    Milestone: 
      :old: 
      :new: Future milestone 2
  ticket_id: 2
  spam: false
  content: 
  user_id: 3
  created_at: 2000-01-03 21:30:00
ticket_changes_004: 
  author: Me
  approved: true
  id: 4
  changes: |
    --- 
    Priority: 
      :old: Normal
      :new: Minor
    Status: 
      :old: Open
      :new: WontFix
  ticket_id: 2
  spam: false
  content: |
    Yes, this is the expected behaviour when you are working with with SVN repositories. Retrospectiva (as a typical RubyOnRails application) uses ~40M of RAM, the rest is consumed by the Ruby-SVN bindings (for various reasons). The memory consumption is directly proportional to the size of your repository, but your demand of ~100M of RAM seems quite reasonable to me.

    Please don’t worry being Out Of Memory after a few days, the memory allocation will not grow any further.

    Regards[[BR]]
    Dimitrij  
  created_at: 2000-01-04 21:30:00
ticket_changes_005: 
  author: Me
  approved: true
  id: 5
  ticket_id: 2
  spam: false
  content: |
    Try to change

    {{{
      @@gc_count = (@@gc_count + 1) % 20
    }}}
    
    to a lower value, eg:

    {{{
      @@gc_count = (@@gc_count + 1) % 10
    }}}

    This should slow-down your memory growth (and the SVN processing speed :-().

  created_at: 2000-01-05 21:30:00
ticket_changes_006: 
  author: Me
  approved: true
  id: 6
  changes: |
    --- 
    Priority: 
      :old: Minor
      :new: Enhancement
    Status: 
      :old: WontFix
      :new: Open
  ticket_id: 2
  spam: false
  content: 
  created_at: 2000-01-06 21:30:00