-
Help with ML in Immich using Intel i3-14100 iGPU
Got it working. Thanks.
-
garfnodie started following Help with ML in Immich using Intel i3-14100 iGPU
-
Help with ML in Immich using Intel i3-14100 iGPU
Intel i3-14100 with 32g of ram. I installed Immich using Compose Manager Plus, got it all installed and working, was able to add photos, search and all. So since the basics were working, I wanted to see what capabilities, if any, I had with my measly integrated gpu. Below is the compse and env files. I added the Intel iGPU part the env, and then I made some edits to the compose file. Since everything was working, and the only changes I made were tot he machine learning section, I know my issues most likely there. I stopped messing with after a bit and decided to come here and see how to fix it. The system has 32Gb of ram, so I'm hoping that can help make up for the paltry gpu. This may be a fool's errand, but I had to at least try as a discreet gpu just isn't going to happen for a long time. If it is truly fruitless, then I could use help just putting the machine learning section back to the defaults. # # WARNING: To install Immich, follow our guide: https://docs.immich.app/install/docker-compose # # Make sure to use the docker-compose.yml of the current release: # # https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml # # The compose file on main may not be compatible with the latest release. name: immich services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} # extends: # file: hwaccel.transcoding.yml # service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding volumes: # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file - ${UPLOAD_LOCATION}:/data - /etc/localtime:/etc/localtime:ro env_file: - .env ports: - '2283:2283' depends_on: - redis - database restart: always healthcheck: disable: false immich-machine-learning: container_name: immich_machine_learning # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag. # Example tag: ${IMMICH_VERSION:-release}-cuda image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}-openvino # extends: # uncomment this section for hardware acceleration - see https://docs.immich.app/features/ml-hardware-acceleration file: hwaccel.ml.yml # service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the -wsl version for WSL2 where applicable deploy: resources: reservations: devices: - driver: openvino count: 1 capabilities: - gpu volumes: - model-cache:/cache env_file: - .env restart: always healthcheck: disable: false redis: container_name: immich_redis image: docker.io/valkey/valkey:9@sha256:c123e3715db63d06d4ad6964884037aa0d5d4d703939b9929954112889708e1d healthcheck: test: redis-cli ping | grep -q PONG || exit 1 restart: always database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23 environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} POSTGRES_INITDB_ARGS: '--data-checksums' # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs # DB_STORAGE_TYPE: 'HDD' volumes: # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file - ${DB_DATA_LOCATION}:/var/lib/postgresql/data shm_size: 128mb restart: always healthcheck: disable: false volumes: model-cache: # You can find documentation for all the supported env variables at https://docs.immich.app/install/environment-variables # The location where your uploaded files are stored UPLOAD_LOCATION=/mnt/user/Personal_Stuff/Immich # The location where your database files are stored. Network shares are not supported for the database DB_DATA_LOCATION=/mnt/user/appdata/postgresql/data # To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List TZ=America/Chicago # The Immich version to use. You can pin this to a specific version like "v2.1.0" IMMICH_VERSION=v3 # Connection secret for postgres. You should change it to a random password # Please use only the characters A-Za-z0-9, without special characters or spaces DB_PASSWORD=postgres # Intel iGPU device=/dev/dri # The values below this line do not need to be changed ################################################################################### DB_USERNAME=postgres DB_DATABASE_NAME=immich
-
New iOS and Android App – U-Manager (Monitor & Control your Unraid Server)
Why though? Why not offer a completely Google free option that doesn't require Google Services or framework.
-
Can I stop the notification bell from always showing the most severe indicator, even when it's a not a new notification?
I'm sorry if I didn't word that title question correctly. I hope my explanation below is easier to understand. When I wake up and look at my Unraid dashboard, I expect at least one notification from "Mover Tuning" saying whether it did or did not transfer any data to the array. The notification for that is just a green circle with a check mark in it. If I haven't deleted or archived past notification though, and there is something with a yellow triangle exclamation from days ago, like say a high cache disk usage, or something from "Fix Common Problems," then the icon will be the yellow triangle, even if those notification were from days ago and I've already seen them. It seems to me that if just clicking the bell to see the notification is enough to reset the bell icon back to the default, then the system has acknowledged that I've see the notification there, and it shouldn't be showing me an indicator for notification from days ago that I've already seen, it should just be whatever has happened since I last clicked the bell. Is there a setting somewhere that change this, or is this a feature request I should submit? Or is this something that is already in the pipeline and I'll just have to wait a bit?
-
Trying to find support forum for binhex-official-byparr app
I'm trying to some help with the binhex-official-byparr container, but I can't find any support forums for them. The support link in the Unraid app center just takes you to the github issues page, but my problem isn't with the app itself, I just can't find a configuration file on my mac to work with it. I don't want to clutter their issue page with an id10t error. I don't use discord, and was hoping someone here knows a good forum for things like byparr, qbittorrent, and other related(🏴☠️) stuff.
-
[Plugin] Appdata Cleanup Plus
Is there any way for me to downgrade to whatever the last version was before this horrible, confusing, and busy redesign?
-
[Plugin] Mover Tuning
Is there an eli5 for this plugin, because I'm not understanding parts of it. In the attached image, I have the description/help box showing for each of the "Mover Tuning - Filters," but the first line in each one just seems like a jumble of words that sort of make sense, but I can't figure out what exactly they each do.
-
[Plugin] Appdata Cleanup Plus
I am really confused by this plugin. I just want to delete the jellyfin stuff that it's showing. the old one I just clicked the checkbox and deleted it. That's all I need to do, but I can't even find a delete button in this thing.
-
Why did the 7.3.0 update come up with Onboarding when booted?
Awesome. Thanks. Good to know.
-
Why did the 7.3.0 update come up with Onboarding when booted?
I'm pretty new to Unraid, having built my system in December. Prior to today, I had only done one OS update to 7.2.5, and after that update, the system just booted, I logged and and continued on. Today, I update to 7.3.0, and upon booting, it comes up with an onboarding thing that I don't even remember from my initial building of the system, and certainly didn't get it last week when I update to 7.2.5. It really freaked me out for a moment because I was afraid I had just royally f*cked something up and killed my nas. Thankfully, just selecting skip was all I needed to do, but good lord did that freak me out. Why did it do that, and why this update and not 7.2.5?
-
Unable to access WebUI. Made no changes.
Awesome. That is most useful. I'll look into the Innodisk for sure.
-
Unable to access WebUI. Made no changes.
Any idea of the quality of the nand used on the 64Gb emmc in Steam Decks? Is it the same lower quality nand used in most flash drives, or does it have similar wear tolerance to regular ssd's? I've been trying to find a good use for it since I replaced it with a 256Gb ssd.
-
Unable to access WebUI. Made no changes.
I guess I don't get why they aren't always on and running continuously by default. You never know when or what is going to happen, and if you only run logs after something happened, how is that going to help you?
-
Unable to access WebUI. Made no changes.
So, don't write to the boot drive if it's a flash drive, which mine is. I don't have a reliable enough remote location, or even a reliable enough network, to go remote. I'm left with local, and since the whole reason I'm at this point, is because I lost access to any shares, using cache/share isn't a good idea. Now I'm just back to USB, only external this time, and since a flash drive isn't recommended, I have to use an external SSD, which just sound like overkill. Maybe I'm missing something here, but is writing the logs to the drive really that bad that i'll kill a flash drive that fast, because otherwise, I don't see a good option for those of us on a shoestring budget.
-
Unable to access WebUI. Made no changes.
It's working. Trying to figure out what happened though.
garfnodie
Members
-
Joined
-
Last visited