Our dedication is paying off – in the past two months, we've witnessed a significant uptick in the popularity our services. Several hosting companies have integrated Releem on a large scale, adding hundreds of servers.
This expansion is a testament to our commitment to improving the performance of customer applications and easing the burden of time-consuming MySQL tuning for engineers.
We're always collecting both issues and feature requests on our GitHub. Here's where you can contribute:
Issues – If you encounter any problems or bugs, report them here.
Feature Requests – Have an idea to make Releem even better? Share your suggestions here.
Updates to Releem Portal
We understand the importance of accessibility for users and MySQL performance observability, which is why we've made some key updates to the Releem Portal:
Improved Log File Size – Our InnoDB Log File Size health check has undergone significant improvements. The old calculations were improperly used the buffer pool to determine redo log size. (Issue #202)
Improved Table Cache Hit Rate – We've also enhanced the Table Cache Hit Rate health check, adjusting the threshold from 20 to 90 for more precise monitoring. This higher threshold aims to prevent cache overflows. (Issue #201)
UI Improvements – We’ve improved the user experience of our initial landing page. Now, when a user logs in to app.releem.com, the system automatically detects the number of servers they have. If there is only one server, the dashboard is opened. If there are multiple, a server list page is opened. Thank you to our user Ryan for this great feature suggestion.
New Help Resources – We've added a new Help window featuring Frequently Asked Questions to assist you in navigating and utilizing Releem more effectively.
Time Zone Adjustments – We’ve fixed the time display issue on the daily graph. Now, configurations will be shown in your local time zone, not UTC+3.
Updates to Releem Platform
Fixed RDS Memory Usage – We fixed the RDS memory usage calculations. Previously, these calculations were based solely on active memory, which did not provide a complete picture according to Amazon RDS documentation. (Issue #212)
Query_cache_type bug – We've identified and resolved a bug in our metrics collection process, which impacted servers with a disabled query_cache. (Issue #214)
Query_cache_size MariaDB issues – We fixed an issue that was causing Releem to recommend impossible values of query_cache_size in MariaDB. (Issue #216)
Updates to Releem Agent
Configuration Automation – We're developing an automated solution for the commonly encountered issue of incorrectly configured opened_files_limit. While we work on this feature request, we encourage you to utilize our documentation to address this issue. (Issue #172)
Community Contributions – A customer has provided a great workaround for running Releem Agent on FreeBSD. (Issue #203)