This is an archive of the discontinued LLVM Phabricator instance.

[clangd] Use in-memory preambles in clangd.
ClosedPublic

Authored by ilya-biryukov on Nov 9 2017, 6:59 AM.

Event Timeline

ilya-biryukov created this revision.Nov 9 2017, 6:59 AM

After looking at the numbers, I think we should make this configurable. I'll update this change accordingly. Not sure what should be the default, though. I'm currently erring on the side of "in-memory by default".

Current implementation eats almost twice as much memory, which quickly adds up (tried comparing with earlier builds on ClangdUnit.cpp).
Even without proper benchmarks, it's clear that if we run out of memory (and we easily could if run on a machine with, say, 8GB of RAM) on-disk preambles are an easy way out of trouble.

sammccall edited edge metadata.Nov 9 2017, 8:04 AM

Heh, I was just going to ask :-)

As a very first step, can we make this configurable but off-by-default? That will address the pressing diskless-servers need.

In a typical workstation scenario, disk is plentiful (if slow) and RAM is scarce - very likely we're running browser + editor (VSCode is another browser really) + clangd + build system, and clangd is likely the least important of these...
So if we're going to increase mem usage by a significant amount I think we want to measure it carefully first.

Made in-memory preambles optional (on-disk by default).

As a very first step, can we make this configurable but off-by-default? That will address the pressing diskless-servers need.

I think on-disk by default makes sense now until we do the measurements and have a the data to prove the on-memory is really better.

sammccall accepted this revision.Nov 15 2017, 3:22 AM

As discussed, we should probably bundle together some related options into structs to make plumbing easier. Not a blocker here though.

If these options are pure-data, I think it's OK if some layers end up with access to other layers' options.

clangd/ClangdUnit.cpp
238

ref is still here :-)

clangd/tool/ClangdMain.cpp
48 ↗(On Diff #122845)

Couple of questions about the flag syntax:

  • I wonder about the granularity - if we had another temp storage (indexes?), would we want another flag or something shared like -in-memory-storage
  • Having this as a bool seems confusing compared to -pch-storage={memory/disk}. (We could also overload such a flag to allow setting the location, but nobody's asked for that yet)
This revision is now accepted and ready to land.Nov 15 2017, 3:22 AM
ilya-biryukov marked an inline comment as done.
  • Removed /*ref*/.
  • Changed the command-line flag: it's -pch-storage now instead of -in-memory-pchs.
  • Actually pass the StoreInMemory flag to PrecompiledPreamble::Build.
  • Fixed a new usage of ClangdServer after rebase (In ClangdTests).
clangd/ClangdUnit.cpp
238

Thx. Missed that. Removed.

clangd/tool/ClangdMain.cpp
48 ↗(On Diff #122845)
  • Indexes are fundamentally different because we actually want to persist them across multiple sessions. But I see your point. I'd go with another flag for greater flexibility. We do want clangd work great by-default, so those flags are mostly for people who know what they're doing and can figure out which flags they want to change and why. Maybe I'm not right, though, and people would want those kinds of switches.
  • Totally like the -pch-storage={memory/disk} more, updated the change accordingly.
This revision was automatically updated to reflect the committed changes.