0

Performance Issues on Ninox – Has Anyone Experienced This?

Hi everyone,

I'm experiencing some performance issues with Ninox and wanted to see if anyone else has had similar experiences and found a solution.

Compared to when I first started using it, it seems to have become significantly slower in displaying data, processing modifications, and synchronizing real-time entries made by operators on tablets. I'm receiving more and more reports of slowness, and the situation seems to be getting worse.

For example, when I open the database, the "Attività" table sometimes doesn’t display any data until I refresh the page. This happens on both PC and mobile devices.

Do you think this could be a server-side or client-side issue? Is there anything I can do to improve performance?

I’ve never really looked into indexes or primary keys, as I assumed Ninox handles these aspects differently from other databases. However, I’m now wondering if there are any best practices or optimizations I should consider.

Since we are relying on Ninox more and more, I’d really like to understand whether these issues can be fixed or if I should start exploring other options.

Thanks in advance to anyone who can share insights! 😊

Mauro

4 replies

null
    • Sviluppatore Ninox
    • Fabio
    • 9 days ago
    • Reported - view

    Hello Mauro.

    Performance slowdowns in Ninox can be caused by various factors, but there are some optimizations you can try to improve efficiency:

    - Optimize queries and formulas:

    • avoid using complex formulas directly in fields, especially if they involve multiple searches in large tables;
    • if possible, store calculated values in dedicated fields instead of recalculating them each time

    - Limit the number of displayed records:

    • if your "Attività" table is large, try filtering the displayed data in views to load only the necessary records.

    - Minimize the use of complex relationships:

    • too many relationships between tables or recursive links can slow down loading times. Ensure that each relationship is truly essential;

    - Optimize triggers and scripts:

    • if you have "On Modify," "On Create," or "On Delete" triggers, check that they do not perform heavy operations unnecessarily;
    • avoid using nested loops or operations that iterate over too many records.

    By applying these optimizations, you can significantly improve the responsiveness of your Ninox database. If the issues persist, consider reaching out to Ninox support to check for possible server-side slowdowns.

    Hope this helps! 😊

     

       Fabio

    • Fred
    • 9 days ago
    • Reported - view

    One thing that caught me out in the beginning is creating formulas and displaying them in the table view. If you can imagine doing that with your Financial table, that forces Ninox to run the code for each record.

    Using dashboards and creating summary tables helps to take the load off Ninox when you are doing charts.

    • Rafael Sanchis
    • Rafael_Sanchis
    • 9 days ago
    • Reported - view

    I am having problems, when I modify a field and save it takes too long, however other times it is not is random.

    • Fred
    • 3 days ago
    • Reported - view

    Take a look at this post. I make a reference at the beginning to how I first tried to do stats and how it ruined my DB.

    Let us know if you are trying to do something similar and maybe we can help redesign things so it runs faster.