fix post
This commit is contained in:
parent
0d63615019
commit
f33181421a
@ -15,15 +15,15 @@ image = "https://gitee.com/flintylemming/mitsea-public-source/raw/master/images/
|
||||
|
||||
人脸识别任务完成后两三个小时都不自动回收显存
|
||||
|
||||

|
||||

|
||||
|
||||
原因非常的抽象,它的前端会定时调 API 的 /check
|
||||
|
||||

|
||||

|
||||
|
||||
然后他后端的重启逻辑是什么呢,只要有 API 调用,就一个小时内都不会重启
|
||||
|
||||

|
||||

|
||||
|
||||
所以他就永远都不会重启释放显存
|
||||
|
||||
@ -31,33 +31,33 @@ image = "https://gitee.com/flintylemming/mitsea-public-source/raw/master/images/
|
||||
|
||||
它的缩略图、元信息提取、生成缩略图等任务有可能不是并行的,至少前端看不出来。导致初始化时扫库效率明显低于 immich(任务调度已经拉满CPU 64 线程)
|
||||
|
||||

|
||||

|
||||
|
||||
immich 多个任务是并行的
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
3. CLIP 搜图模型效果不佳
|
||||
|
||||
默认用的 Chinese-CLIP 而且不能更换,实测效果不如 immich 的 XLM-Roberta-Large-Vit-B-16Plus。比如搜索血压计,MT Photos 搜不出来
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
4. 文档质量一般
|
||||
|
||||
首先他这个 docker compose 配置文件写的就不合理,两个依赖的 ai 容器根本就不需要开放端口,直接用 compose 内部网络就可以链接,即 `容器名:端口`
|
||||
|
||||

|
||||

|
||||
|
||||
然后他本来是基于 docker compose 提供的部署教程,这里又变成了 docker run,第一次用的用户可能就不知道这个 --gpu all 如果你改 docker compose 里面的镜像,还需要添加 GPU 设备才可以
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
总而言之就是非常混乱,你不如直接给四个 docker compose 配置文件:不带 AI 的,带 onnx AI 的,带 cuda AI 的,带 arm AI 的就完事了。不要把面向客户的文档写成了自己看的笔记。
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user