i was perusing the nextcloud forums in github and came across this:
https://github.com/nextcloud-snap/nextcloud-snap/issues/1935 to improve the speed of photo rendering
there are a few other issues talking about the same thing, but i was wondering what the default limit is set thru syncloud and if it’d be worthwhile to play around with the php memory setting using this command:
sudo snap set nextcloud php.memory-limit=256M
wanted to ask before I broke something…
512M already if I set this correctly:
I think the best thing is to use more powerful cpu like Syncloud N 
ah, thanks. I’m actually running Syncloud on an ATOM MINI-ITX w/VGA, LVDS, DP, 2GbE, J1900 (Celeron) with 8GB RAM/512GB mSATA
a bit more power than the Syncloud N i think. But not a full PC performance.
Right now I’m only using it for Nextcloud and Syncthing.
Probably not much to improve going to 1024 or 2048 MB?
thanks
steve
Can you run this command:
openssl speed -engine padlock -evp aes-256-cbc -multi 1
And with number of cores you have
openssl speed -engine padlock -evp aes-256-cbc -multi [cores]
openssl speed -engine padlock -evp aes-256-cbc -multi 1
engine "padlock" set.
+DT:aes-256-cbc:3:16
+R:5789502:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:64
+R:1574378:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:256
+R:404991:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:1024
+R:102015:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:8192
+R:12782:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:16384
+R:6392:aes-256-cbc:3.000000
Got: +H:16:64:256:1024:8192:16384 from 0
Got: +F:22:aes-256-cbc:30877344.00:33586730.67:34559232.00:34821120.00:34903381.33:34908842.67 from 0
OpenSSL 1.1.1d 10 Sep 2019
built on: Mon Apr 20 20:23:01 2020 UTC
options:bn(64,64) rc4(16x,int) des(int) aes(partial) blowfish(ptr)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-8Ocme2/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
evp 30877.34k 33586.73k 34559.23k 34821.12k 34903.38k 34908.84k
openssl speed -engine padlock -evp aes-256-cbc -multi 4
Forked child 0
Forked child 1
Forked child 2
Forked child 3
engine "padlock" set.
engine "padlock" set.
engine "padlock" set.
+DT:aes-256-cbc:3:16
+DT:aes-256-cbc:3:16
+DT:aes-256-cbc:3:16
engine "padlock" set.
+DT:aes-256-cbc:3:16
+R:5811658:aes-256-cbc:3.000000
+R:5811396:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:64
+DT:aes-256-cbc:3:64
+R:5611833:aes-256-cbc:2.990000
+DT:aes-256-cbc:3:64
+R:5785560:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:64
+R:1451911:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:256
+R:1525279:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:256
+R:1549590:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:256
+R:1438149:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:256
+R:284567:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:1024
+R:326412:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:1024
+R:325258:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:1024
+R:259406:aes-256-cbc:3.010000
+DT:aes-256-cbc:3:1024
+R:74819:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:8192
+R:80268:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:8192
+R:79433:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:8192
+R:79234:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:8192
+R:11147:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:16384
+R:10662:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:16384
+R:9993:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:16384
+R:10322:aes-256-cbc:3.000000
+DT:aes-256-cbc:3:16384
+R:6392:aes-256-cbc:3.000000
+R:6392:aes-256-cbc:3.000000
Got: +H:16:64:256:1024:8192:16384 from 0
Got: +F:22:aes-256-cbc:30029875.59:32539285.33:27853824.00:27398144.00:29114368.00:34908842.67 from 0
+R:6387:aes-256-cbc:3.000000
+R:6389:aes-256-cbc:3.000000
Got: +H:16:64:256:1024:8192:16384 from 1
Got: +F:22:aes-256-cbc:30995509.33:33057920.00:22062437.21:27045205.33:28185941.33:34892458.67 from 1
Got: +H:16:64:256:1024:8192:16384 from 2
Got: +F:22:aes-256-cbc:30856320.00:30680512.00:27755349.33:27113130.67:27287552.00:34881536.00 from 2
Got: +H:16:64:256:1024:8192:16384 from 3
Got: +F:22:aes-256-cbc:30994112.00:30974101.33:24283050.67:25538218.67:30438741.33:34908842.67 from 3
OpenSSL 1.1.1d 10 Sep 2019
built on: Mon Apr 20 20:23:01 2020 UTC
options:bn(64,64) rc4(16x,int) des(int) aes(partial) blowfish(ptr)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-8Ocme2/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
evp 122875.82k 127251.82k 101954.66k 107094.70k 115026.60k 139591.68k
Well that puts you somewhere between Syncloud H and Syncloud S far away from Syncloud N.
Interesting, I would have thought a more PC type board would give better results. I guess the j1900 celeron chip is a bit old (released in 2013). I see the ‘N’ is based on an I3 chip so no wonder.
Do you have comparison graphs (easier for me to gage the differences)?
Other than a fresh install, Is there a simple way to migrate all of the data if at some point I choose to upgrade?
Cpu comparison is this: Performance · syncloud/platform Wiki · GitHub
Some doc on migration: Device migration · syncloud/platform Wiki · GitHub
Also you can always try VirtualBox VM on a powerful Intel/Amd if you already have one (but cannot convert to a server a use for something else) to see if more performance solves your user experience issues.