continue
continue copied to clipboard
100% CPU Usage
Type: Bug
When working in the bun.js repo continue uses 100% CPU and lags vscode.
Extension version: 0.8.12 VS Code version: Code 1.86.1 (Universal) (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:09:01.236Z) OS version: Darwin arm64 23.3.0 Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Apple M3 Max (16 x 24) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | 3, 3, 5 |
| Memory (System) | 48.00GB (13.61GB free) |
| Process Argv | --crash-reporter-id a6d5c417-5383-434f-bf6f-25fcdc099f89 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
bf62j303:30959262
b1063948:30958189
3ef8e399:30964150
bg6jg535:30958357
@gvilums this is the local indexing process. Can disable in config.json with "disableIndexing": true or by choosing a remote embeddings provider like OpenAI (https://continue.dev/docs/walkthroughs/codebase-embeddings#openai).
Button to pause indexing in the UI is coming soon to further address this, then a bit later ideally we'll go for GPU-accelerated embeddings
Is there a way to move this to a separate process so that it doesn't lag the vscode extension process?
yeah, good call. no reason why not
@sestinj can you assign this to me ?
I think another approach could be allowing to disable indexing on large projects. While we do have a 'disableIndexing' configuration in config.json, could we also have an option to disable indexing in the project's setting.json?
@kevinarch This can be achieved with a .continuerc.json in the root of your workspace: https://docs.continue.dev/reference/config