Nomie 6 is slow when one has much data

[allo-]

Nomie 6 is much slower than Nomie 5 when one imports a lot of data from a v5 instance. The dashboard page is especially slow, maybe depending on the types of dashboards (e.g. how many days are displayed).

When I open the dashboard page after having imported the data, the whole page turns unresponsive.
I think some other parts of the webapp are also slow, but I didn't test it thoroughly yet, as I for the moment only wanted to keep using nomie and thus sticked with v5. But in the long run, Nomie 6 should be able to handle amounts of data that were no problem in Nomie 5.

[donalmacanri]

Can you give me an idea of how much data you have in Nomie? Around how many entries and how many different trackables? I'm trying to put together a large enough data set to test with.

[allo-]

• Trackers: 20
• Events: 8942
• People: 10
• Dashboards: 2
  1. Widgets: 14
  2. Widgets: 9

Possibly relevant dashboards:

• A few 7 Days linecharts for range trackers like mood
• A few 30 Days linechars for range trackers like mood
• A few 7 Days bar charts for event trackers like coffee and persons
• A few 30 Days bar charts for event trackers like coffee and persons
• A few 7 Days line charts for time trackers like sleep
• A few 30 Days line charts for time trackers like sleep
• A few 7 Days bar charts for time trackers like sleep
• A few 30 Days bar charts for time trackers like sleep
• 2 year bar chart (aggregating values into month bars) for a time trackers
• 1 90 day bar charts (not aggregating values) for an event tracker
• 1 90 day bar chart (not aggregating values) for a range tracker
• 2 Min/Max widgets for range trackers

Examples could be:

• 30 day line chart of sleep time
• 30 day bar chart of number of coffees
• 90 day bar chart of sleep time
• year bar chart of sleep time (showing monthly sums)

Many of them are logged almost daily.

Browser: Mobile Vivaldi (Chromium based) for using Nomie as PWA.

I don't like to share actual data, but if you have more questions about the structure I can extract the numbers or similar meta-data from the exported json.

[donalmacanri]

Excellent, thank you! No, I don't want to ask anyone to share data, my goal is to create to a useful synthetic dataset for testing. Will let you know if I have any other questions.

[ipsquiggle]

I too am notice some very poor responsiveness in V6. I'm running in Chrome/PWA on android 13.

It's not obvious that this has to do with my amount of data, but I definitely do have a lot of it. It's also worth noting that some of my logs are quite long, upwards of 500 words. I know this would sometimes lead to unresponsiveness in v5 as well.

Here is a screencast showing the lack of responsiveness. I'm basically just smoothly scrolling my thumb up and down the whole time, then side to side at the end. The app is not smoothly scrolling.

https://photos.app.goo.gl/e8igf8YJsbHz4Kho9

Please let me know if there's anything else I can share to help diagnose this. It appears chrome for android doesn't have any developer tools, I'll try this on PC later and see if I get similar issues.

[allo-]

I don't have any long entries. I mostly track events and people with context tags and short comments (usually less than 20 additional characters).

[donalmacanri]

Just coming back to this since I've got a bit more familiar with how data is stored and queried. @allo- is it specifically dashboards and widgets that are slow for you, or any other areas of the application slow as well? For example ... is the main Tracking functionality responsive for you? Does the Timeline tab load and behave as you would expect?

[allo-]

I had mainly the problem with the dashboard, but I think I also had one either in the events list or on the trackers page one time. I had the app that unresponsive that it was hard to test in more detail, when opening it each time got it to hang.

I could try to test importing json with dashboards removed and doing some actions or similar when it's helpful.

[donalmacanri]

I could try to test importing json with dashboards removed and doing some actions or similar when it's helpful.

That would definitely be help isolate the issue, if you get a chance.