Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
O
OBITools3
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 14
    • Issues 14
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • OBITools
  • OBITools3
  • Issues
  • #67

Closed
Open
Opened Apr 10, 2019 by Celine Mercier@mercier 
  • Report abuse
  • New issue
Report abuse New issue

obi clean efficiency

obi clean behaves unpredictably on huge datasets, sometimes using a lot of memory or spending a lot of computation time in the tsearch library. Replacing the tsearch library with my AVL tree implementation for example could fix those issues.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
critical enhancement
Assign labels
  • View labels
Reference: obitools/obitools3#67