Multiple PhotoPrism processes #1667
Replies: 3 comments 8 replies
-
Multiple photoprism processesYes, it is mostly safe to run multiple instances unless you somehow manage to trigger the rendering of the same thumbnail file in two different processes or use SQLite. This can lead to an error or a panic. You should notice it. Try to avoid indexing with more than one instance. Our Getting Started docs on this:
Face Untagging
2900? PhotoPrism's face recognition is designed to recognize family members and friends, not an entire village. If you are referring to unrecognized faces (face clusters), then you can expect a decrease in the number once you have recognized some. In the database, https://github.com/photoprism/photoprism/blob/develop/internal/entity/marker.go#L37 What specifically do you mean with "changes I committed"? Did you directly modify the database tables? There is an exception for very, very, very similar face embeddings that should belong to the same person. If there is conflicting information, the subject UID may be cleared, as an automatic decision is not possible with conventional math. It will trigger a warning so it does not go unnoticed and you do not have to guess if this is the case: photoprism/internal/entity/face.go Line 167 in c3ab42e |
Beta Was this translation helpful? Give feedback.
-
|
see https://docs.photoprism.org/getting-started/config-options/#facial-recognition for technical details on facial recognition incl links to related research papers |
Beta Was this translation helpful? Give feedback.
-
|
You read it wrong. I meant a person's face count went from 2900 to 700
s3nt fr0m a $martph0ne, excuse typ0s
…On Wed, 1 Dec, 2021, 22:05 Michael Mayer, ***@***.***> wrote:
Multiple photoprism processes
Yes, it is mostly safe to run multiple instances unless you somehow manage
to trigger the rendering of the same thumbnail file in two different
processes or use SQLite. This can lead to an error or a panic. You should
notice it. Try to avoid indexing with more than one instance.
Our Getting Started docs on this:
For example, relying on database locking and conflict resolution tends to
be inefficient with an increasing number of cores and workers. On the other
hand, this simplifies application logic, especially when running multiple
instances on the same index.
Face Untagging
Today, I noticed that my face's count dropped from 2900 to 700. I had
spent a lot of time manually tagging a lot of my faces. I'm surprised that
PhotoPrism has overridden some of the changes I committed.
2900? PhotoPrism's face recognition is designed to recognize family
members and friends, not an entire village. If you are referring to
unrecognized faces (face clusters), then you can expect a decrease in the
number once you have recognized some.
In the database, markers.subj_src is set to manual for manually matched
face markers to avoid overwriting changes:
https://github.com/photoprism/photoprism/blob/develop/internal/entity/marker.go#L37
What specifically do you mean with "changes I committed"? Did you directly
modify the database tables?
There is an exception for very, very, very similar face embeddings that
should belong to the same person. If there is conflicting information, the
subject UID may be cleared, as an automatic decision is not possible with
conventional math.
It will trigger a warning so it does not go unnoticed and you do not have
to guess if this is the case:
https://github.com/photoprism/photoprism/blob/c3ab42eff4c505989e72540673297d926d0e608e/internal/entity/face.go#L167
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1667 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAP7SGVZJ3BXP7Z7WVN7LLUOZFFDANCNFSM5GVC6VAA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Oh, for a single person! They were all matched manually? Still sounds too much. This would also create a massive overhead when comparing. PhotoPrism therefore merges manual single face clusters into larger clusters based on multiple manual matches. This is all pretty complex, so if your question is if there could be a bug or unhandled edge case... Probably yes. In particular if face embeddings are hard to distinguish. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. It was for a single person. The anomaly happens once in a while and
some previously, manually tagged faces to a person, get lost.
I think, correction over time, has lowered the occurrence.
s3nt fr0m a $martph0ne, excuse typ0s
…On Sat, 4 Dec, 2021, 13:30 Michael Mayer, ***@***.***> wrote:
Oh, for a single person! They were all matched manually? Still sounds too
much. This would also create a massive overhead when comparing. PhotoPrism
therefore merges manual single face clusters into larger clusters based on
multiple manual matches. This is all pretty complex, so if your question is
if there could be a bug or unhandled edge case... Probably yes. In
particular if face embeddings are hard to distinguish.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1667 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAP7SCJJNR7NWH6BHGXFL3UPHDBFANCNFSM5GVC6VAA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
What is the issue relating to matching many faces manually in one batch? I am guilty of this. |
Beta Was this translation helpful? Give feedback.
-
|
What do you mean with batch? Batch editing isn't implemented yet 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Simultaneous changes are always problematic as they can lead to timing issues and all sorts of inconsistent states. We did our best to prevent it in the UI, so make sure to always use the latest stable version. |
Beta Was this translation helpful? Give feedback.
-
I was referring to your comment on 04/12/2021 "Also make sure not to match too many faces manually in one batch". I meant manually assigning unassigned faces to subjects of multiple photos manually in one sitting. |
Beta Was this translation helpful? Give feedback.
-
I am using latest version (which only allows one face assignment at a time). But I have done this in the past prior to the UI restricting multiple face assignments in quick successions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've titled this discussion about multiple processes but this thread is more about multiple observations I've had lately.
Multiple photoprism processes
I have a couple of systemd service units that I've created to invoke certain jobs in a timely manner, namely:
index -cindex -f -ccleanuppurgeindex -f -cis scheduled to runweeklywhile others run at different times in the day.At times, I've noticed that there are multiple
photoprismprocesses running on the live system.Is this a normal behavior ? What if, at this point I do a
docker execand run another photoprism housekeeping command ? Does PhotoPrism deal with multiple processes safely ?Face Untagging
Over the weekend, with some minor tweaks and code changes (mostly a revert of children detection), I finally managed to complete tagging all the pictures in my photo collection with PhotoPrism. I also spent a couple of hours validating the categorized faces to ensure most of it was correct.
Today, I noticed that my face's count dropped from 2900 to 700. I had spent a lot of time manually tagging a lot of my faces. I'm surprised that PhotoPrism has overridden some of the changes I committed.
In the logs, I see many messages of the type below:
I haven't seen PhotoPrism throw any error or such but the behaviors I mentioned above look erratic. Can people here please enlighten on the observations I have and if I'm doing anything foolishly wrong ? Or is it just some corner case bugs in PhotoPrism ? Under what condition would face counts decrease ?
Note: An example service below (
index -f -c). None of my services have errored out.Beta Was this translation helpful? Give feedback.
All reactions