haskell/haskell-ide-engine

Is it normal for hie to take ~4GB of memory per instance?

Open

#665 opened on Jun 28, 2018

View on GitHub
 (8 comments) (5 reactions) (0 assignees)Haskell (205 forks)batch import
component: documentationgardening 🌱good first issuehelp wanted

Repository metrics

Stars
 (2,358 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I currently have a workflow where I usually have a couple different projects open, each of them has the VSCode integration with hie. I find that each editor has it's own hie process and that process takes about 4G of RAM. Is this typical/expected or is something in my setup wrong/different than others?

Contributor guide

Research direction
Profile memory usage of hie when opening multiple projects in VSCode. Use memory profiling tools like GHC's hm or heap profiling to identify memory leaks or inefficiencies.
Tech stack
haskell
Domain
toolingdeveloper experience
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Haskell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75