Comment to 'The need for speed'
  • Hello @Andrey Yasko ,

    It would be great if you could share a recommended recipe for mysqld.cnfhttps://github.com/unacms/UNA/blob/master/scripts/docker-compose/mysqld.cnf Is this configuration sufficient, or are additional settings required? How can we best reproduce the same performance results?

    Is the database server running as a cluster or within Docker? Are the volumes managed by Docker, or are you using OS-managed disks? What filesystem do you recommend for SSDs? Do you use RAID, and if so, is it software or hardware RAID? Are you relying on SAN or another storage architecture? A complete optimization recipe would be incredibly useful.

    In addition, it would help to have configuration guidelines not only for MySQL but also for the other components for example, storage of files under the storage directory. Is this running on a separate server and mounted as a network filesystem, or do you recommend a different setup? Ideally, storage should function independently from the main system could you share your preferred solution?

    Also, is UNA typically deployed in Docker containers, a custom cluster, or Kubernetes? Any guidance or best practices here would be very helpful for the whole community.

    Could you also clarify whether UNA currently uses file cache or memcached? I would like to experiment with DragonflyDB and Redis, and I have a working recipe with the Valkey fork using both a Caddy proxy and Nginx reverse proxy. My results have been 100%, 100%, 100%, 100% in Lighthouse across all four categories for my main site: https://www.coozila.com/plus/view-video/coozila-screencast-from-20-06-25

    Of course, my main site is not UNA I’m using nodejs for the backend, with Vite for the frontend. Initially, my intention was to build a Vite-based interface for UNA that would connect via API to the UNA backend. However, since learning that NEO will be released, I decided to stop this work especially considering that UNA is also integrated with mobile applications, so my approach could turn into redundant effort in the wrong direction. Instead, I’m waiting for NEO to become available, as I believe it will be much more effective to align with it and contribute to the NEO frontend at that point.

    I am now preparing a recipe to reproduce and further improve performance for UNA. For this purpose, I’ll be forking UNA on GitHub and suggesting patches. There is still quite a bit of work ahead, but we’re not far I believe I can contribute substantial improvements to help UNA fronted achieve 100% across all Lighthouse categories. I’m also involved in other projects, but I’ll dedicate part of my time to UNA within the time available, as I feel the platform is now very close to being fully polished.

    One more question: does this recipe include NEO, or is it designed to work without NEO as UNA standard?

    Thank you! and congratulations for your performance.