If your server runs out of memory, the index is frequently locked, or other system resources are running low: This will result in a much faster solution than waiting for a core team member to remotely analyze your problem and then provide a fix. That being said, one of the advantages of open-source software is that users can submit pull requests with performance and other enhancements they would like to see implemented. GitHub Discussions or any of our other public forums and communities are great places to start a discussion. We kindly ask you not to open a problem report on GitHub Issues for poor performance on older hardware until a full cause and feasibility analysis has been performed. Since these can prove to be very time-consuming and cost-intensive in practice, users and developers must decide on a case-by-case basis whether this provides sufficient benefit in relation to the costs or whether the use of more powerful hardware is faster and cheaper overall. In many cases, performance can be improved through optimizations. Like most applications, PhotoPrism has certain requirements and our development process does not include testing on unsupported or unusual hardware. It is a known issue that the user interface and backend operations, especially face recognition, can be slow or even crash on older hardware due to a lack of resources. Although their hardware gets faster with each generation,īenchmarks show that even 8-year-old standard desktop CPUs like the Intel Core i3-4130 are often many times faster: Optimized for minimal power consumption and low production costs. Your instance to a more powerful device or cloud server may help. If you've tried everything else, then only moving Last but not least, performance can be limited by your server CPU. We take no responsibilityįor instability or performance problems if your device does not meet the requirements. RAW image conversion and TensorFlow are disabled on systems with 1 GB or less memory. Switching to SSDs makes a big difference, especially for write operations and when the read cache is not the cost savings from using slow hard disks are minimal.due to the HDD seek time, HDDs only support 5% of the reads per second of SSDs.SSDs have more predictable performance and can handle more concurrent requests.database performance extremely benefits from high throughput which HDDs can't provide.Local Solid-State Drives (SSDs) are best for databases Solve Windows-Specific Issues › Storage ¶ However, this does not guarantee that all issues such as missing indexes are resolved. It may help to run the migrations manually in a terminal using the migrations subcommands. If this is the case, please make sure that your migrated database schema matches that of a fresh, non-migrated installation. As such, they have not been officially released, recommended, or extensively tested by us. The instructions for these migrations were provided by a contributor and are not part of the original software distribution. For example, MariaDB cannot process rows with text columns in memory and always uses temporary tables on disk if there are any. Migration from SQLite ¶Īfter migrating from SQLite, it is possible that columns do not have exactly the data type they should have or that indexes are missing. In case PhotoPrism and MariaDB are running in a virtual machine, its memory size should be increased as well. Otherwise, they may run out of resources and cannot benefit from a larger cache size. If you are using Docker Desktop on Windows or macOS, remember to increase the total memory available for Docker services.
0 Comments
Leave a Reply. |