Navigation Menu

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

Wikilinking becomes very slow in larger gardens #906

Closed
flancian opened this issue Jan 11, 2022 · 4 comments
Closed

Wikilinking becomes very slow in larger gardens #906

flancian opened this issue Jan 11, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@flancian
Copy link

  • Foam version: 0.17.2
  • Platform: Linux
  • Issue occur on the foam template repo: No

Summary
Wikilinking anything in my digital garden takes ~5-10s, apparently due to autocomplete delays.

What's worse, if I keep typing while vscode is hanging (in the case in which I know in advance which node I want / I do not really need autocomplete), my input gets garbled when it eventually shows up on screen -- square brackets are often added in the wrong positions in the string I just wrote.

I can reproduce in both an i7-8565U and a Ryzen 5900, not state of the art but not exactly old machines either.

Steps to reproduce

  1. Grow a garden with more than 4k nodes, like e.g. anagora.org/go/flancian/garden
  2. Try to wikilink anything :)

Additional information

  • the Foam log in VsCode (see instructions)
    • just learnt about this and changed the level to debug, will attach in an update.

Thank you!

@flancian flancian added the bug Something isn't working label Jan 11, 2022
@DrakeWhu
Copy link

DrakeWhu commented Jan 11, 2022

Hey, I've been having some performance issues with my graph specially, not with linking yet. My garden is over 1k notes so I'd like to know if we can solve this so we won't have any problem with large gardens. I don't have much time now but I'd like to help with this, I think the support of big gardens should be a priority after the API is released.

@HaloWang
Copy link

Also find the latency of typing in vscode is increased after I show my project's graph. Actually I want a d3.js-like graph which might be hard to be integrated into VSCode.

@riccardoferretti
Copy link
Collaborator

Yeah I think we need to take a look at performance optimization, @DrakeWhu if you are interested in taking a stab, I would be happy to support as best as I can

@riccardoferretti
Copy link
Collaborator

Closed for inactivity

@riccardoferretti riccardoferretti closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants