Skip to content

Support to process in multithreading #53

@webysther

Description

@webysther

Allow process using multiple CPU's to be more fast, for my case with 21k stacks this take ages. This don't use any resources at all to justify being serial.

Command being timed: "docker run -it --rm -e LOG_LEVEL=warn --name immich-stack ghcr.io/majorfi/immich-stack:latest --dry-run --api-key REDACTED --api-url REDACTED"
User time (seconds): 0.28
System time (seconds): 0.05
Percent of CPU this job got: 0%
Elapsed (wall clock) time (h:mm:ss or m:ss): 35:40.11
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 25708
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 3471
Voluntary context switches: 1881
Involuntary context switches: 4
Swaps: 0
File system inputs: 208
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0

21234 stacks
86916 assets
35 minutes

This can be reduced using MT in at least 10x less time.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions