# Version 1.1.0 in docker: excessive CPU usage **URL:** \ **Category:** šŸŖ² Bug\ **Created:** [September 21, 2022, 11:13pm UTC](https://forum.photostructure.com/t/version-1-1-0-in-docker-excessive-cpu-usage/1678 "2022-09-21T23:13:46Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![adept](https://forum.photostructure.com/user_avatar/forum.photostructure.com/adept/32/486_2.png) [@adept](https://forum.photostructure.com/u/adept)\ **Post date:** [September 21, 2022, 11:13pm UTC](https://forum.photostructure.com/t/version-1-1-0-in-docker-excessive-cpu-usage/1678/1 "2022-09-21T23:13:46Z")
Hi! I am running photostructure in docker from the image photostructure/server:stable which gives me version 1.1.0, according to the About page. Some time ago I reported a [bug in 1.0.0-beta9](https://forum.photostructure.com/t/1-0-0-beta-9-is-ready/693/17) where sync process would sit in some sort of loop reading /proc/self/stat and consuming CPU cycles. @mrm replied there that problem is reproducible, but I donā€™t know whether it was fixed in the end or not. Iā€™ve now upgraded to 1.1.0 and the behavior is still there, except CPU usage is now higher than before. this is except from ā€˜topā€™ for the photostructure sync process started 6 days ago: ```auto PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND 8504 adept 29 9 370.3m 87.7m 13.1 0.3 1351:18 S PhotoStructure sync ``` Note high TIME and 13% CPU. There is nothing going on in the photstructure at the moment - nothing to import, web UI is not opened, and ā€œphotostructure logtailā€ just shows ā€œService(web) --health-check { ok: ā€¦ā€ messages from time to time. And yet sync process consumes 13% CPU around the clock ā˜¹ Strace summary of about 10 seconds: ```auto # strace -f -c -p 8504 strace: Process 8504 attached with 11 threads ^Cstrace: Process 8504 detached strace: Process 8505 detached strace: Process 8506 detached strace: Process 8507 detached strace: Process 8508 detached strace: Process 8509 detached strace: Process 8510 detached strace: Process 8515 detached strace: Process 8516 detached strace: Process 8517 detached strace: Process 8518 detached % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 99.67 2.948000 15849 186 11 futex 0.17 0.005080 2 3045 epoll_pwait 0.09 0.002682 0 20284 open 0.05 0.001460 0 20292 read 0.02 0.000676 0 20284 close 0.00 0.000000 0 8 write 0.00 0.000000 0 24 mmap 0.00 0.000000 0 24 munmap 0.00 0.000000 0 8 getpid ------ ----------- ----------- --------- --------- ---------------- 100.00 2.957898 64155 11 total ``` Excerpt from the ā€œstrace -f -ttā€: ```auto [pid 8504] 00:07:07.799877 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.799948 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.800027 close(26) = 0 [pid 8504] 00:07:07.800111 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.800182 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.800251 close(26) = 0 [pid 8504] 00:07:07.800387 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.800456 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.800522 close(26) = 0 [pid 8504] 00:07:07.800605 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.800676 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.800746 close(26) = 0 [pid 8504] 00:07:07.800890 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.800987 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.801057 close(26) = 0 [pid 8504] 00:07:07.801152 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.801243 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.801309 close(26) = 0 [pid 8504] 00:07:07.801444 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.801513 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 [pid 8504] 00:07:07.801580 close(26) = 0 [pid 8504] 00:07:07.801662 open("/proc/self/stat", O_RDONLY|O_LARGEFILE) = 26 [pid 8504] 00:07:07.801732 read(26, "25217 (PhotoStructure ) R 28 21 "..., 1023) = 395 ``` ## Expected Behavior I would expect photostructure not to check /proc/self/stat million times each second šŸ™‚ ## Environment Operating system and version: Docker 20.10.3 on the Synology box PhotoStructure edition: docker ---
**Author:** ![adept](https://forum.photostructure.com/user_avatar/forum.photostructure.com/adept/32/486_2.png) [@adept](https://forum.photostructure.com/u/adept)\ **Post date:** [September 21, 2022, 11:35pm UTC](https://forum.photostructure.com/t/version-1-1-0-in-docker-excessive-cpu-usage/1678/2 "2022-09-21T23:35:28Z")
ā€¦ aaaaand it looks like if I restart the container, it sometimes end up in this state, and sometimes does not. ā€œlogtailā€ does not show anything interesting ā˜¹ ---
**Author:** ![mrm](https://forum.photostructure.com/user_avatar/forum.photostructure.com/mrm/32/1881_2.png) [@mrm](https://forum.photostructure.com/u/mrm)\ **Post date:** [September 22, 2022, 12:08am UTC](https://forum.photostructure.com/t/version-1-1-0-in-docker-excessive-cpu-usage/1678/3 "2022-09-22T00:08:52Z")
Hey there @adept ! I suspect this is `node` reading from `/proc/self/stat` to get CPU usageā€“in v1.1 I was trying to be ā€œcleverā€ with CPU usage, and self-throttle based on statistics I could gather every second or two. With v2.1 Iā€™m using `renice` to make sure PhotoStructure is well-behaved (and an analogous approach for Windows users), which should be a much lighter weight (and more reliable) solution. You could try running the latest v2.x alpha on your Synologyā€“Iā€™ve rewritten the work scheduler, db persistence, parallelism, and added a ton of new features. Just update the image name to `photostructure/server:alpha`. **Alpha/beta caveats apply:** > [@Alpha, beta, stable, and latest; What should you use?](https://forum.photostructure.com/t/alpha-beta-stable-and-latest-what-should-you-use/274): > > Hereā€™s a question I got today over email: Iā€™m having a hard time figuring out which version I should be using. Iā€™m currently running PhotoStructure as a docker container. I am using the ā€œbetaā€ tag in the docker compose file. Is that correct? TL;DR: Please do not run alpha or beta builds unless: you have frequent, automatic backups of your data, and youā€™re willing to report bugs that you see to either discord or this forum. If youā€™re unsure, please use stable PhotoStructureā€™s relā€¦