Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate memory consumption #718

Open
alandefreitas opened this issue Oct 28, 2024 · 0 comments
Open

Investigate memory consumption #718

alandefreitas opened this issue Oct 28, 2024 · 0 comments

Comments

@alandefreitas
Copy link
Collaborator

Clang processes one TU at a time while Mr. Docs accumulates data with each TU. For instance, if you compile 100 TUs and each produces 100 unique Info, then Mr. Docs stores 10,000 Info.

There are three broad classes of programs:

  1. those which will fit into memory comfortably
  2. those which are strained to fit into memory
  3. those which simply do not fit into memory

We are targeting 1 now. We can target 2 by optimizing how much we store (for example, storing less). We have yet to do anything for 3, and it is unclear that we should attempt to do so now, although it is a reasonable long-term goal.

Yes. It's not a problem we have right now with our examples. We could measure things to see how it's going for now or test the limits by trying to generate documentation for something large, like LLVM.

.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Accepted
Development

No branches or pull requests

1 participant