![]() ![]() Install MariaDBįirst of all you need to install MariaDB, now one of the stipulations of Nextcloud is that it requires binary logging to be enabled on the MariaDB server. MYSQL_PASSWORD: 'Keep it secret, keep it safe!'Īliasgroup1: " server_name: " seems to generate a lot of questions and queries so thought I’d do a quick walkthrough. MYSQL_ROOT_PASSWORD: 'Keep it secret, keep it safe!' nextcloud-storage/nc-web-data/:/data/ # This is actually a folder on a RAID 5 storage array ![]() Image: "linuxserver/nextcloud:amd64-latest" Here is my docker-compose.yaml file hopefully that make it a bit clearer -ĭNSPLUGIN: # see documentation: Thanks to Docker/Docker Compose this was extremely easy, and it solved my performance issues. are now on essentially a solid-state device. I adjusted by docker-compose file volumes so that only the Nextcould DATA folder was storing files to the RAID 5 array, but everything else, all the other volumes, where storing “locally” to the Virtual Machine’s storage. What that means is that the “harddrive” on the Virtual Machine is solid-state. I have a solid-state PCI harddive on my server, and that is actually where my Virtual Machine is housed. The RAID controller checks out fine, and so what I ended up doing was splitting out the storage. Thanks to 's suggestion, I looked at the RAID 5 setup I have on the server. I have essentially moved my Nextcloud Docker containers from one machine to another with more resources, yet my performance is drastically worseĪny ideas on how to troubleshoot this? Or anyone run into something similar? Why would only my Nextcloud Docker container be so drastically impacted by a move from one machine to another? I have since added Redis for caching with no noticeable impact. All other Nextcloud Docker Containers (letsencrypt, mariadb, redis, collabora) on the VM stay below 1% when idle. The CPU usage via docker stats for the Nextcloud web container is always 8% and fluctuates between 16%-24% when idle. Using docker stats the CPU for the Nextcloud web container, and all other Nextcloud-related Docker containers was below 1% with the occasional spike higher.Īfter moving Nextcloud to the Virtual Machine inside the HP ProLiant Server, pages take 7-10 seconds to load, and the “Load” under Administration → System is always above 2.0 usually between 2.5 - 5.8. Additionally, I only had local Memcache/APCu set up. On the Lenovo ThinkCenter, the Nextcloud UI pages loads were under 1 second, and the “Load” under Administration → System was only between 0.15 - 0.80. I only have two users of my Nextcloud instance. Storage: 45 GB for OS and passthrough to host's 1.2 TB storage for persistent Docker volumes I split out a portion of HP ProLiant Server for a NixOS VM to be used as the new host for my Nextcloud Docker Containers using libvirt/KVM/virtmanager. I recently acquired an HP ProLiant D元60 G7: CPU x2: Intel(R) Xeon(R) CPU X5650 2.67GHz (6 cores / 2 threads) My Nextcloud setup has Maria DB 10.6.12 running in its own container for the database, and a letsencrypt container to proxy traffic.Īll of this is connected via a Docker Compose File. I had Nextcloud 25.0.3 running in a Docker Container on a Lenovo ThinkCenter: CPU: Intel(R) Core(TM) i3-4130T CPU 2.90GHz (4 cores) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |