RSSOwl Performance & Footprint Tasks

From RSSOwl

Contents 1 Lazy loading of News-Description 2 Virtual Trees 3 Do not keep News-State in indexed documents of Lucene 4 Retention Policy

Lazy loading of News-Description

• Idea: Only load Description of News when actually displayed
• Pros
• Cons
• Benchmarks
• Status: Under investigation

Virtual Trees

• Idea: Use a virtual Tree for the Feed-View Headline-Table
• Pros
• Cons
  • Yet a lot of Bugs
  • Sorting/Filtering must take place in the ContentProvider
• Benchmarks
• Status: Wait for 3.3 M3

Do not keep News-State in indexed documents of Lucene

• Idea: Use the DB for queries that involve the state of a News. This will reduce re-indexing when News-States change.
• Pros
• Cons
  • What about queries that involve both State- and Content-Fields?
• Benchmarks
• Status

Retention Policy

• Idea: Automatically delete News that match a certain polics (read / old / > 100 News /...)
• Pros
• Cons
• Benchmarks
• Status: Implemented for M3