With more and more attachment, Each start consumes a high cpu

[charleslu]

I hope this problem is just me, someone else has seen this post and can help me test it if possible.
Both computers in my home have been tested with related issues, so I think it is a BUG while bringing it up
If you also have questions, I will write down my solution for the convenience of people who have the same problem as me

It is convenient for users who do not want to put pictures on the network, but can directly paste files to obsidian users quickly
Use My - Easy - Pic - Bed build local map Bed
Then upload all PNGS to the local map bed using obsidian-image-auto-upload-plugin.
In this way, even if you replace the computer, as long as obsidian and My-Easy-Pic-Bed are copied, you can use it normally on another device, without relying on network storage

[hhtmp88]

I see the same problem, when I gradually move my Joplin notes to Obsidian.

When I finished moving, and there are 10,391 files, 1311 folders, in my vault.

and this cause big problems in Obsidian Android, it crash suddenly and cause a series of problems, the major problem is:

• some of the changes to a note cannot be synchronized (I use the plugin “Remotely save” to sync to Storj S3-compatible storage, it has no such problem when the number of attachments and notes are low)

• newly added notes may not be in sync

[charleslu]

I’m not the only one who met them. I found them in the forums

Bug: Opening a vault causes excessive access to IndexedDB (LevelDB), resulting in 100% CPU usage

Steps to reproduce Open a large vault on macOS Open Activity Monitor and inspect the CPU usage of Obsidian.app Did you follow the troubleshooting guide? [Y/N] Yes. The issue can be replicated with the Sandbox vault, see the steps in “Additional information” below. Expected result CPU usage should return to very low percentages once the vault is fully opened. Actual result CPU usage stays near 100% for several minutes. For large vaults, high CPU usage can even remain for over one hour. E…

[ob_fan]

What about let Obsidian just startup, and do the indexing after startup?

This seems a way to improve the user experience for the case with tens of thousands of files in the vault. Because no one needs all the files instantly after startup, if obsidian needs more time indexing more files, why not let the indexing happens after we have started it?

I have more than 40k files in my vault currently, and 37k are images. I did economic analysis with obsidian and like the easiness with ![[Imange file name]] to quote the trend pic I need. This helps alot. But everytime Obsidian startup takes more than 2 minutes, maybe it spends the time indexing the image file names? But why it is the same everytime it startup? Why not let it just startup, and do the indexing after startup?

[WhiteNoise]

It’s what already happens

Both the one time indexing and high cpu use lamented in this thread happen after startup.

You have another problem.

[Smithy]

Slightly on/off topic, I’m a bit frustrated that obsidian takes so long to open.

With around 1k notes and loads of images, it takes 10-15 secs to open on my faster pc, and over 30 secs on my older one

[WhiteNoise]

@Smithy Turn Restricted mode on, and restart obsidian, how long does it take?

Where is you vault stored? (Do you use icloud or similar services?)

How many files total are we talking about?

[Smithy]

@WhiteNoise thanks for your suggestion. I’ve just converted my older Win10 laptop into a Linux machine. Newbie so it took me a while to get it all up and running.

Funny thing is, I just timed it and it now takes 8 seconds. Hmm. I turned on Restricted Mode and it took 4 seconds.

It’s on Dropbox via Cryptomator, and with about 1k notes.

Anyhow, it’s MUCH faster on Fedora Linux obviously so I’m happy with that.

[indigofairyx]

Hi yall, first post here.

ditto and this high cpu usage

im a “noob” to obsidian. (and markdown) been trying to figure it out for about a week or so.
trying get myself out of MS OneNote,

obsidian seems great on paper… buuttt… lets save 4 different web clippers not working for another day.

thou, this is not okay…

---

i recently exported my onenote lib of ~2850 .md files, ~37,300 files total with the images that came with it.

it takes obsidian about 2 - 3 minutes to launch.

i can load steam and video game
and\or
reboot my entire system (will all these extras on start up) faster than i can open obsidian. let alone leave it running.

also seems be stuck indexing the last ~300 files for two day. or it cant index them and wont skip them.

ive turned off

• indexing
• ocr
• omniserch.
• sandboxed vault
• disabled/restricted all plugins
• disabled themes
• a couple other tweak i saw in this forum
• even tried poking around in the dev console looking for the memory leak, but that a bit over my head, found this a couple other minor errors
  

and nothing seem to make a difference on the performance hit I’m taking. it might drop obsidian cpu leak by 2%

my desktop isn’t a rocket ship but its fairly powerful with and i7 6700 and 64g ram.

a text editor shouldn’t impact it this much.

from a few post i found this seems to be a common know issuse.

which i unfortunate because its not usable like this.

soo i don’t know…

is there a way to move images outside of the vault and still link them locally?

some more debug info…

SYSTEM INFO:
	Obsidian version: v1.5.12
	Installer version: v1.5.12
	Operating system: Windows 10 Pro 10.0.19045
	Login status: not logged in
	Insider build toggle: off
	Live preview: on
	Base theme: dark
	Community theme: MagicUser v19.7.0
	Snippets enabled: 0
	Restricted mode: off
	Plugins installed: 54
	Plugins enabled: 42
		1: Importer v1.6.1
		2: Iconize v2.12.0
		3: Text Extractor v0.5.1
		4: Hotkey Helper v0.3.18
		5: Editor Syntax Highlight v0.1.3
		6: Recent Files v1.3.10
		7: Excel to Markdown Table v0.4.0
		8: Style Settings v1.0.8
		9: Export Image plugin v2.3.10
		10: Image Context Menus v1.7.0
		11: Customizable Menu v2.2.0
		12: Better Word Count v0.10.1
		13: Colored Text v1.0.0
		14: File Tree Alternative v2.5.7
		15: Extract url content v0.12.1
		16: Editing Toolbar v2.4.16
		17: Settings Search v1.3.10
		18: Image in Editor v2.2.6
		19: Templater v2.3.1
		20: Plugin Update Tracker v1.5.2
		21: Automatic Table Of Contents v1.3.2
		22: Auto Split v1.1.2
		23: Paste Link v1.0.1
		24: Table of Contents v0.2.0
		25: Slash Commander v0.2.16
		26: Reveal Active File Button v2.0.3
		27: markdown export v1.0.20
		28: File Info Panel v1.3
		29: Open vault in VSCode v1.2.2
		30: Favorite Note v1.0.4
		31: Prominent Bookmarked Files v2.0.2
		32: Time Ruler v2.3.0
		33: TagFolder v0.18.7
		34: Dataview v0.5.66
		35: CSV Table v1.2.0
		36: Commander v0.5.1
		37: Keyboard Analyzer v0.1.3
		38: Open Plugin Settings v1.3.2
		39: Local Images Plus v0.15.9
		40: Settings profiles v0.5.7
		41: Emoji Toolbar v0.4.1
		42: Omnisearch v1.22.2

[WhiteNoise]

@indigofairyx

it takes obsidian about 2 - 3 minutes to launch.

Does it mean it takes 2 or 3 minutes until you can edit your notes?
Or is it just the cpu usage that lasts a long time when you start Obsidian but you can edit your notes right away?

[indigofairyx]

Both…

it will show

• load plugins (for about 3 seconds)
• loading caches (quickly)
• loading workspace (see screenshot) for 1 or 2 minutes

it stay on this loading workspace for 1 or 2 mins with my cpu around 60+% then even after i get to my notes views Obsidian.exe at ideal will hover between 13 - 18% usage by itself. more than everything else running in my system combined.

there are 4 sub-process running under it. the one using the 13+% has this string in the command line

[0] C:\Users\CLOUDEN\AppData\Local\Programs\obsidian\Obsidian.exe

[1] --type=renderer

[2] --user-data-dir=C:\Users\CLOUDEN\AppData\Roaming\obsidian

[3] --standard-schemes=app

[4] --secure-schemes=app

[5] --fetch-schemes=app

[6] --streaming-schemes=app

[7] --code-cache-schemes=app

[8] --app-path=C:\Users\CLOUDEN\AppData\Local\Programs\obsidian\resources\app.asar

[9] --no-sandbox

[10] --no-zygote

[11] --node-integration-in-worker

[12] --first-renderer-process

[13] --lang=en-US

[14] --device-scale-factor=1.25

[15] --num-raster-threads=4

[16] --enable-main-frame-before-activation

[17] --renderer-client-id=4

[18] --time-ticks-at-unix-epoch=-1716246183783808

[19] --launch-time-ticks=92596434743

[20] --mojo-platform-channel-handle=2464

[21] --field-trial-handle=1760,i,9093950161867953379,1935381593532139452,262144

[22] --enable-features=SharedArrayBuffer,kWebSQLAccess

[23] --disable-features=SpareRendererForSitePerProcess,WinDelaySpellcheckServiceInit,WinRetrieveSuggestionsOnlyOnDemand

[24] --variations-seed-version

[25] /prefetch:1

[FULL] "C:\Users\CLOUDEN\AppData\Local\Programs\obsidian\Obsidian.exe" --type=renderer --user-data-dir="C:\Users\CLOUDEN\AppData\Roaming\obsidian" --standard-schemes=app --secure-schemes=app --fetch-schemes=app --streaming-schemes=app --code-cache-schemes=app --app-path="C:\Users\CLOUDEN\AppData\Local\Programs\obsidian\resources\app.asar" --no-sandbox --no-zygote --node-integration-in-worker --first-renderer-process --lang=en-US --device-scale-factor=1.25 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=4 --time-ticks-at-unix-epoch=-1716246183783808 --launch-time-ticks=92596434743 --mojo-platform-channel-handle=2464 --field-trial-handle=1760,i,9093950161867953379,1935381593532139452,262144 --enable-features=SharedArrayBuffer,kWebSQLAccess --disable-features=SpareRendererForSitePerProcess,WinDelaySpellcheckServiceInit,WinRetrieveSuggestionsOnlyOnDemand --variations-seed-version /prefetch:1

its using a ton of ram too. but i have 64gig (overkill) on my ram, so that not causing a noticeable effect on my system.

but regarding the cpu usage. i can notice when obsidian is running, everything else in my system slow down.

[WhiteNoise]

Ok, you have a different problem than thr one discussed in this thread, which I am going to close.

Kindly open a bug report and follow ALL the instructions there.