Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • F FEDOT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITMO-NSS-team
  • FEDOT
  • Issues
  • #230

Closed
Open
Created Jan 25, 2021 by Elizaveta Lutsenko@LizLutsenkoOwner

Add profiling for debug mode

Created by: J3FALL

Looks like fedot do not correctly work with memory, and MemoryError occurs when:

  • GPComposer operates with deep chains (see issue #183 (closed))
  • Dataset is too large
  • Available models in composer are too "heavy"

In order to discover this problem, it is required to:

  1. Check how to use profiling libraries (see https://github.com/sberbank-ai-lab/LightAutoML for example)
  2. Adapt profiler for composer
  3. Check memory/cpu usages during composition on "heavy" configurations
  4. Find memory leaks and provide a new solution
Assignee
Assign to
Time tracking