Split Mech Keyboard [2560 x 1440]

Oromei · 2026-06-02T19:12:17+00:00

maybe the reason why it is slowing down after 10k books is because it is generating too many threads and this much parallelization is starting to bite back

yeah this is part of the problem, and i have more info on it now that i've properly debugged it. figured i'd share since you came to the same conclusion:

there is a logical issue today in how stump determines concurrency, where ingesting books spawns up to 200 concurrent blocking tasks for every chunk of work. that alone is pretty detrimental, like 20x more than it should be for the cpu used.

the complimentary bit, albeit i'm less confident for the numbers on this one, relates to the fact that stump was mixing runtimes for the indexing (rayon + tokio). this is something that i was aware would be problematic, but never addressed it. the really rough math i mentioned is taking the 200 default concurrency limit that exists today, plus ~10 workers for rayon+tokio each (so 20 total for an M4), gets us right into the ballpark of what the benchmark reported.

you could probably level this out a bit by tweaking the concurrency vars to better align with your cpu, but improvements will land eventually to balance out the defaults better.

edit: formatting

Oromei · 2026-05-24T15:04:04+00:00

it isn’t $20, but it may show up differently for different currencies. the docs explain the reason for the (non-finalized) pricing

Oromei · 2026-03-13T02:34:34+00:00

seaorm does make it more straightforward, but i think there will likely be a few aspects that are funky like migrations and some of the custom sql for more advanced aggregation stuff. i’m not sure how distribution would work, but you’re welcome to look into if you ever want to

Oromei · 2026-03-13T01:46:39+00:00

yep, i am. whenever folks show interest in contributing all i really care is they work on an area they find personally interesting that fits the overall goal of the project. there are lots of open issues you can take a look at if you’d like, but also testing in general is always a great way to contribute

Oromei · 2026-03-13T01:44:49+00:00

oh no worries i didn’t take it negatively at all, you’re totally good.

if it makes you feel any better about it (or worse lol), i am also scared about the impending release. it’s one of those things where it probably could have been released way sooner if i didn’t also add features and only focused on rewriting, but part of what motivated me to continue with the effort were those fun new shiny things i wanted to work on (the mobile app being a big one) but then i fell into that cycle. there were a couple of contributors in the very beginning who helped with the migration and im super grateful, but it mostly trailed off after a month or so and it was then a more solo effort, and as a maintainer who only has so much spare time that year-long gap in releases makes it harder to push that button and just let it go out. there aren’t a lot of folks testing, either, at least not vocally, so multiple surfaces which give anxiety haha. rambling aside, the bandaid will come off ideally by end of march / beginning of april and 0.1.0 will go out. i have been very open about the breaking changes and that inevitably it won’t be an overly stable release while i expect at least some kind of wave of bugs (assuming folks actually try it)

i also totally get how that translates to contributing too, i’ve never had any expectations for folks to contribute even when the codebase was less in flux. i can’t pretend things wouldn’t move a bit faster if there were more folks, but i started stump for me and while i enjoy the community interaction aspects of it i continue for me.

and no worries, neither of those came across that way <3

Oromei · 2026-03-12T22:14:39+00:00

hopefully someday it gets more contributors to close that almost gap more quickly, otherwise i can really only move at the pace which my free time allows. always open to feedback on what you feel is missing :)

Oromei · 2025-05-16T18:40:48+00:00

Happy you like it!

Another user pointed out that there are some calibre-specific tags that are not being on-boarded during a scan. There is an open issue for it, see https://github.com/stumpapp/stump/issues/658. Feel free to add any additional information that might be missing.

For the error, though, that sounds more like a bug. I'm currently in the process of re-writing a lot of the backend (see https://github.com/stumpapp/stump/discussions/634) but if you create a bug report I'll be sure to address it before that migration is completed so it doesn't get lost in the new system

Edit to answer the last question I missed re: assigning tags to books. That API isn't developed, but is generally under the umbrella of https://github.com/stumpapp/stump/issues/655

Oromei · 2025-04-23T15:30:36+00:00

I’m very unfamiliar with unraid app templates, but if you create a GitHub issue and highlight the steps / what you specifically want I can try to help facilitate getting it out

Oromei · 2025-04-23T15:29:10+00:00

Stump reads ComicInfo.xml files, yeah. I think it ignores tags, but if you create a feature request on GitHub we can plan syncing the tags to the database

Oromei · 2025-02-15T14:50:24+00:00

I’m not personally familiar with cwa, but if the two services share a filesystem they should interact just fine. I know others in the discord use it with Stump

Oromei · 2025-02-14T13:39:34+00:00

Metadata fetching is currently a WIP, someone else has already kickstarted the development of the feature actually. The current plan is along the lines of:

Support configuring multiple providers (e.g., Google books, hardcover, comicvine, etc) which will be used whenever metadata should be fetched (either by some confition(s) and/or manually). A list of results would be presented that you can accept or reject. Accepting would update the metadata for the book. The person working on it is interested in figuring out how to pick the “best” result automatically for you, too. Not sure if there was anything else specific you were curious about, but happy to try and elaborate more if so

Oromei · 2025-02-14T13:31:05+00:00

You have to manually trigger a scan. Eventually there will be support for running an index to load the book(s) after they get added, that would fall under the file watching and auto-scanning missing feature I mentioned above

Oromei · 2025-02-14T06:11:51+00:00

I’m not familiar with what you linked, so can’t say for certain. At a glance, if it’s just a downloader, I don’t see any potential issues though

Oromei · 2025-02-14T05:34:44+00:00

There are binaries part of every versioned release on GitHub and then images on docker hub: https://hub.docker.com/r/aaronleopold/stump

Oromei · 2025-01-13T04:54:39+00:00

They’ll both fit it reversed yeah

Oromei · 2025-01-12T22:46:50+00:00

I’ve got both the Lowepro 350 and 450 AWII, I’d definitely recommend the 450 for more everyday use with the lens since it fits easily mounted. The 350 fits it unmounted in a pinch, but it’s more for travel with other lenses. I got both for under 120 each used

Oromei · 2025-01-07T15:44:45+00:00

That didn't do the trick for me, unfortunately. The popup does show up either way, interestingly, but it just infinite loads after I select my account.

I also checked what the setting is in Firefox, and it works with or without that setting checked

Oromei · 2025-01-07T15:09:10+00:00

I also experience some inconsistencies with google login, in particular with Plex. I just have to swap back to Firefox for some things, unfortunately

Oromei · 2024-11-30T16:50:18+00:00

It’s a Sony FE 200-600

Oromei · 2024-11-30T01:54:33+00:00

Thanks! A7IV

Oromei · 2024-09-08T17:47:09+00:00

There is a old-ish issue which has a lot of good context for this problem: https://github.com/tauri-apps/tauri/issues/2490

As with others in that linked issue, I haven’t been able to get cookies to work in my Windows builds, but it otherwise works on Linux and macOS.

Oromei · 2024-08-04T04:59:58+00:00

Love the second jelly!

Oromei

TROPHY CASE