Timer, speed when saving or changing

[bwie]

Timer, speed when saving or changing. Is there a way to speed up data access?

[reinerj]

Can you explain a little more what issue you have?

Thanks

[bwie]

It takes a long time for a task to start in the timer. The same gild for changes. The data is provided faster in the report. Nextcloud runs in a Docker container with Maria database.

[reinerj]

Can you give a little more information like, is NC installed on Docker, What OS you are using, which PHP version, how many projects you have to track. This would be helpful.

Thanks

[bwie]

Thank you for the willingness to help me with my problem.
TimeTracker is a very good time tracking tool for us. We want to use it more.
Enclosed the detailed information about the system and software environment.
Thanks for your help!

NAS

Modellbezeichnung Qnap TS-677CPU AMD Ryzen 5 1600 Six-Core Processor (6 Kerne, 12 Threads) Gesamtspeicher 40 GB (39 GB nutzbar) Speichersteckplätze 4 (16 GB / 4 GB / 16 GB / 4 GB)
Firmware-Version 4.4.1.1216 Build 20200214

Docker

ContainerStation Version 2.0.957

Container:
Nextcloudweb_1
nextcloudletsencrypt-companion_1
nextcloudapp_1
nextcloudcron_1nextcloudproxy_1
nextcloudredis_1nextclouddb_1
nextcloudcollabora_1

Nextcloud

Nextcloud Version 18.0.1

PHP

Version: 7.3.14
Arbeitspeicher-Grenzwert: 512 MB
Maximale Ausführungszeit: 3600
Maximale Größe zum Hochladen: 2 MB

Datenbank

Art: mysqlVersion: 10.4.8, Größe: 318,8 MB

TimeTracker

Projects = 18
Clients = 15
Tags = 13
Tasks = 73

[puthre]

@bwie starting and stopping a timer should happen instantly. I suspect there is a configuration issue (like maybe the nextcloud server tries to resolve the mariadb server by name and it takes a long time?). The starting (or stopping of the timer) is just a matter of posting a ajax query to the server which in turn does a simple insert (or update) in the database. This normally happens in a matter of milliseconds.

[zeroepix]

Do you have a lot of timed tasks showing up? I found that the more I had, the slower the response. It's much faster when I just make it retrieve the last 7 days only (manual edit)

[digger-bw]

i'm facing this issue as well. I've not that much entry but it needs unreasonable more time with every entry.

i'm currently working on #37 in a separate test-app i'll check if it is the same with changed rendering.

[puthre]

Are you still experiencing this issue?

[zeroepix]

It still is the case. I believe it's an issue related to the ajax refresh whenever something is updated. If you start a work interval, it sends the message to the back-end, then does a full refresh of all the work intervals (slow). If you end a work interval, it sends the message to the back-end, then does a full refresh of all the work intervals. The same for any text or time update.

I circumvent this by setting it to only retrieve the last 7 days, but it's still a minor inconvenience. Does it really need to do that refresh every time? The UI should already reflect the changes based on the user's actions, so if it could be skipped, it will feel a lot more snappy.

[puthre]

Might be fixed by 6bd1e5a

[31SFX4]

I also find starting and stopping very slow, often several seconds.
My setup is Nextcloud 20.0.4. PHP 7.3.19; mysql 10.3.27.
@puthre: the (possible) fix is not in the app store yet, it seems?

[31SFX4]

Still a problem in version 0.47.

[31SFX4]

This seems to get worse. It now often takes more than 15 seconds to respond when I start or stop a timer or delete an older entry. Also Firefox gives me a warning "the website is slowing down your browser" and resource usage goes up to 30 or 40%.
So the problem must be somewhere in the browser code, not the server scripts or database access.

It wasn't so bad before, but I don't know if this was due to code changes or because I now have more entries or something else.

Is there anything I can do to help diagnose this?

[31SFX4]

This is related to the number of entries that are shown in the timer view. If I set the filter to "today" (8 entries), then starting/stopping takes about 1 second, if I set it to "last 5 years" (a few hundred entries I guess) then it takes 40 seconds.

[puthre]

@smatthie What is your client specs? Does Chrome show the same issue?