Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rust Glancer: Rust LSP using 100x less RAM

rust-glancer.github.io

Post reply on HN
Print view View original

71–80 of 129 posts

Re: Rust Glancer: Rust LSP using 100x less RAM

#71

Post by IshKebab »

UltraSane wrote: post #60
hofiflo wrote: post #55

I personally don’t agree with “LLMs are just a tool” but I’m honestly impressed by the author’s description of LLM usage and taking the responsibility for the code. IMHO, without having looked at the code base itself, this sounds like a pretty healthy way to approach LLM usage!

"I personally don’t agree with “LLMs are just a tool”" Then what are they?

They're a new category of thing. They aren't really "just an" anything.

When the wheel was invented cavemen probably said "it's just a stone".

Re: Rust Glancer: Rust LSP using 100x less RAM

#72

Post by Fluorescence »

dijit wrote: post #42
Paria_Stark wrote: post #41

While I respect the work behind rust-analyzer greatly and think it's a good part of how cool the language is, I will NEVER understand the design decision to flat out refuse using disk cache. I understand the argument that implementing this puts less pressure behind speeding up the indexing process, but honestly with the price of ram today I'm tired of the memory and cpu usage each rust-analyzer process takes up. Espe…

rust-analyzer taking 2GiB of RAM per instance definitely hurts. And I agree that efforts to reduce this are noble and warranted, but I worry about what doesn’t happen because of those optimisations. The rust tooling is just so-so good (and a better argument for the language than memory safety imo), so I support more efforts to be ergonomic over memory optimisation. Even though rust-analyzer is often the largest memor…

It wasn't long ago RA was consuming over 24GB for my main workspace.

They've been working on memory use and it dropped to ~7.5GB for a while but the last couple of releases have been nudging up again - currently 9.4GB without major change in the workspace.

It becomes an obstacle on a 64GB machine given I work with multiple workspaces open e.g. for the crates I am using, example projects, other branches etc. so I have to start/stop it when I just want basic type-info/navigation. Trialling a different editor alongside my current one becomes prohibitive when it's going to want another 10GB for it's own RA instance.

99% of the code isn't changing so disk caching does seem like a no-brainer like back in the 90s with intellisense .ncb files... just without the regular corruptions though!

Re: Rust Glancer: Rust LSP using 100x less RAM

#74

Post by juntz »

phplovesong wrote: post #52
juntz wrote: post #38

wonderful IDEA! Often two much ram cost using nvim with LSP, it may be work! Forking it!

Hostile fork!

Oh I'm sorry for that...I just want to express the appreciation. So if you don't mind, could you tell me why this would looks like some Malicious comments.

I'm new for the opensource project, if there any impolite for the "fork",I would like to apologize for everyone here

Re: Rust Glancer: Rust LSP using 100x less RAM

#75

Post by popzxc »

nijave wrote: post #69
dijit wrote: post #42

Earlier quoted context omitted.

rust-analyzer taking 2GiB of RAM per instance definitely hurts. And I agree that efforts to reduce this are noble and warranted, but I worry about what doesn’t happen because of those optimisations. The rust tooling is just so-so good (and a better argument for the language than memory safety imo), so I support more efforts to be ergonomic over memory optimisation. Even though rust-analyzer is often the largest memor…

I would think there has to be some decent middle ground like storing some structures on disk mmap'd and letting the kernel handle back pressure and caching

Storing structures mmapp'd is actually very tricky. I have experimented with rkyv initially having this idea in mind, but gave up because the machinery just to power the archive types was causing complexity to explode. The thing with zero-deserialization frameworks is that they are very limited in what they can abstract away, and it gets ugly pretty quickly.

So I don't deny the idea, just stating that it's probably _significantly_ more complex to implement than it sounds.

Re: Rust Glancer: Rust LSP using 100x less RAM

#76

Post by juntz »

phplovesong wrote: post #52
juntz wrote: post #38

wonderful IDEA! Often two much ram cost using nvim with LSP, it may be work! Forking it!

Hostile fork!

I will appreciate for your generous sharing,it will help me much.

Learning how to communicate here is the most important things right now for me. But I have no idea about how is the polite here. I want to express more just like all the others but I don't know how to do.

if you would like to help me, thanks a lot!

Re: Rust Glancer: Rust LSP using 100x less RAM

#77

Post by 762237 »

tiagod wrote: post #73
762236 wrote: post #3

Why don't people explain their acronyms? What is a Rust LSP?

Why don't people use Google for such incredibly simple questions instead of asking the comment section?

It wasn't a request for information, since you can obviously look it up. It was a critique on people's inability to imagine their audience, particularly once it scales.

Re: Rust Glancer: Rust LSP using 100x less RAM

#78

Post by 762237 »

verandaguy wrote: post #27
762237 wrote: post #25

Earlier quoted context omitted.

We sample it, and upon finding problems, adjust the system to eliminate that class of problems in the future.

Did you just create a new account so you could keep arguing with people?

Yes. HN is groupthink central, and enforces it through down votes, which marks the account as low quality, which then turns off commenting for that account. It is a classic negative feedback loop that enforces the groupthink. You can tell how many accounts I've created by the account number.

Re: Rust Glancer: Rust LSP using 100x less RAM

#79

Post by boredumb »

this is awesome and I hope this gains some real steam, we're building everything in rust and locally if i'm watching youtube and running a build+tests and my vscodium starts running the analyzer at the same time I've seen my machine stutter out as it eats up the memory.
Post reply on HN