Skip to content

Performance Bottlnecks #1414

Oct 1, 2023 · 1 comments · 2 replies
Discussion options

You must be logged in to vote

Have to think a bit then lol, I'm usually the one doing performance improvs in our Rust core directly (not counting improvements on our libs used by core). Our most intensive loads are on some jobs, like the indexer job which needs to walk through possibly massive directories and subdirectories. Also, the media processor job have a bunch of CPU-bound work to extract media data and generate thumbnails. The later one possibly has some low-hanging fruits to be taken, like some missing tokio::spawn_blocking to process blocking CPU stuff outside from tokio's futures executor.

The indexer is a bit harder to improve, I had to introduce a bunch of strategies to achieve an OK scalability with it. …

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@gorentbarak
Comment options

@fogodev
Comment options

Answer selected by HeavenVolkoff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants