myDBR 6.1 - "High performace cache support with Redis"

(12 posts) (3 voices)

Tags:

No tags yet.

  1. myDBR Team, Key Master

    myDBR Team is happy to announce the availability of the myDBR 6.1 release.

    myDBR 6.1 brings Redis cache support for myDBR alongside other improvements.

    New functionality:

    • Redis support (OEM version)
    • Dynamic title parameters for reports (OEM version)
    • $mydbr_defaults['db_connection']['disable_writes_to_db'] flag to support running myDBR against a read replica
    • ChartDirector 7.0 support
    • Chart.js 3.5 support
    • Custom defaultView support in the Calendar
    • One can now customize the CSS classes via mydbr_defaults, when constructing the mail for email clients that have limited HTML mail support
    • Improved user group handling in Custom authentication
    • myDBR use of curl now supports redirects

    Fixes and general improvements:

    • MySQL password length increased to support the latest MySQL versions
    • Improvements to linked report error checking

    As always, you can update to the new version using the myDBR's automatic updater.

    Happy reporting,
    --
    myDBR Team

  2. conscience, Member

    Is this Redis support is not available in Premium License?

  3. myDBR Team, Key Master

    Redis support is.available in the OEM version. Installations with many concurrent users benefit the most from it.


    myDBR Team

  4. maron, Member

    Where can OEM users find documentation for this feature?

  5. myDBR Team, Key Master

    The documentation page can be found here.

    Using the Redis cache is very straightforward. Install Redis, point myDBR to Redis and select the reprorts that will take anvantage of the caching. You should be up in 10 minutes.

    --
    myDBR Team

  6. maron, Member

    Thanks.

    Please note that synchronisation is not updated to handle this,

    Incorrect number of arguments for PROCEDURE AhaMerchants.sp_MyDBR_sync_mydbr_reports; expected 15, got 13

    I have updated both versions to check, sp_MyDBR_sync_mydbr_reports has been updated with 2 cache parameters but the sync script does not create them.

    Cheers,
    Maron

  7. maron, Member

    Also we get another error after working around this one:

    Unknown column 'inuse_cache' in 'field list'

    Line 69 in sp_MyDBR_sync_mydbr_reports

    cache_expire = inuse_cache

    Should probably be

    cache_expire = in_cache_expire

  8. myDBR Team, Key Master

    Thank you for reporting this. The latest build should fix the issue.

    --
    myDBR Team

  9. maron, Member

    I have php-redis installed (redis server is separate) and am using it extensively in another application on the same server, however PHP redis shows as not installed in Environment settings.

    Is there anything else that is required?

    Another thing, if we could configure read replica only per report that would be amazing (in this case we would have to configure both read and write host in setup). I would say 95% of our reports are read only (and often only sub-reports used inline are handling writing). Keeping writes on a separate server is going to be strange from a UX perspective.

  10. maron, Member

    Using phphinfo I get the following:

    Redis Support enabled
    Redis Version 4.2.0
    Available serializers php, igbinary

  11. myDBR Team, Key Master

    Do you get the "Install the Redis PHP-extension to use Redis" notification in Environment settings?

    The prerequisite for the Redis showing up is that you are running the OEM version and that you have PhpRedis installed (myDBR will check that the Redis-class is available).

    --
    myDBR Team

  12. maron, Member

    Please disregard this, issue is fixed - I was working on the wrong server.


Reply

You must log in to post.