toby666123

Here you go:    Just as a live example: Had my stash scrape all Performer data yesterday evening. After scraping, the docker container consumed ~300MB RAM. Now, 18h...

Further info, maybe this helps for investigation: RAM usage seems to go down sometimes, just noticed this by coincidence. RAM is now "down" to 794 MB. 

Did exactely as you described: - Restartet the container, it consumed 16 MB RAM ~1 min after start - Ran a Generate task (have some corrupt files throwing lots of...

After restarting the Docker container: 

Will re-do the test with the generate task tomorrow and post the log here. It will be big though, last time the log file was 29MB.... Regarding Scan: I am...

Alright, understood. Makes sense now that I got it. :) And good to know w/ phashes in Scan, you are right of course. :) Do you still need the log...

@bnkai The settings were exactly as shown above in the screenshot, 1 parallel task only. The task ran over 7 corrupt video files. Unfortunately I am on vacation since today...

Any news on this, do you have a rough assumption maybe for when the new docker images will become available? Thanks a lot for your efforts!!

Thanks for the hint! At least a workaround to retrieve the different StashDB images after a Performer has been created. Nevertheless, I think a direct integration into the Performer Edit...

> I'm close to being able to wrap up the project independently (build-from-source excluded) > > I would love to have some testers that have > > * Intel ARC...