ferenci84

> @ferenci84 looks like it's still per-tab as opposed to per session, possible PR is on the wrong branch? @RomneyDa I just didn't push the latest commit. Corrected now.

Provided a Fix for VS code in this PR: https://github.com/continuedev/continue/pull/4161 Please note that if there is a problem with IntelliJ, an equivalent solutions should be provided for that too, until...

I later found that the core problem, that my system's resources got busy in that specific repository, was not solved after applying cache to diff. I traversed the problem and...

@hdtvnase2k Right, the solution need to be adapted. The cache is implemented only for vs code this is the fallback for IDEs where it's not present: `const currentTimestamp = ide.getLastFileSaveTimestamp...

I have made a PR for intelliJ that adds caching for git diff: https://github.com/continuedev/continue/pull/4753 I hope it resolves the issue.

While at it, i noticed an other, possibly related performance issue. Even if there is no user action, getOpenFiles and getWorkspaceDirs are called every few seconds: The pattern is apparent...

@lkk214 I agree with you. I made the simplest possible implementation, but I hope the whole git diff stuff will be taken out from the autocomplete in the future (or...

@sestinj Would you mind to share your opinion about this?

@sestinj This issue seems to cause serious problems especially for people with large java projects. Generating diffs in those projects can get really slow and can make the extension unusable....

@bdavj Not sure if it's working with your version but I'm using this config: ```json "tabAutocompleteOptions": { "maxPromptTokens": 1024, "debounceDelay": 500, "maxSuffixPercentage": 0.2, "prefixPercentage": 0.3, "experimental_includeClipboard": false, "experimental_includeRecentlyVisitedRanges": true, "experimental_includeRecentlyEditedRanges":...