Remove server delay on input
complete
Aleksandr Ladenko
When you write any text - there is a delay in input, up to 2 seconds!
Sometimes there is such a freeze, and then all the written text - appears at once.
Ie clearly takes the server delay factor.
Why do this? Why limit my input, checking information on the server?
Input should be local, and sync with the server only in the background, without interrupting my interaction.
I only need a response from the server when I use the "/" command or something similar...
I see a lot of reports about performance improvements, but in the last couple of years - didn't feel any changes, because if the server is far away, any operation - takes up to 2 seconds of time... Even if you just write a text...
Also, for some reason, the history of activity in some, certain tasks can be loaded for 15-20 seconds! While in others the download occurs in 3-5 seconds.
Log In
Brent
complete
Hi all - the input delay in was fixed with the ClickUp 3.0 update last year. We appreciate your patience and feedback. Closing this out now!
M
Michaël Zappalà
Related to Aleksandr Ladenko initial post
Isn't it a good remark generalisable for a lot of actions ?
For exemple, when changing status, date, anything of a task, it could be done instantaneously locally and the synced with the server.
Then if errors happen a notification can be send to the user.
The user may have the possibilty to check the logs of notification (right now they just disappear and if you missed it, you just know that something bad happend 😅)
I've the impression that it would make the whole experience much more better for the user.
What's your thoughts about it ?
Michael
Yes, still having this issue, and it has become quite prevalent. I see that Justin Hunter said some solutions were in the works back in April, so, any update on this at all? For example, I work in a doc to brainstorm, and let's say I create a task from a snippet of line. Once I hit enter, it is 3 to 4 seconds (sometimes more) before I can click on another line to begin working on the next thing. Or, if I open up a task to begin working on something, it is 2 to 4 seconds (or more) of staring at the screen before I can actually change the status or click the timer.
Please advise as to when this will be fully resolved.
Ambroise Dhenain
Glad to this being worked on, that was my biggest "Ugh" moment when I discovered ClickUp a few days ago. Made me miss Asana, despite their editor lacking so many critical features.
Justin Hunter
in progress
Hey all! As mentioned, we have a variety of solutions to fix this. Two of them are being worked on in tandem and will be released soon.
Justin Hunter
Hey Aleksandr Ladenko! That's definitely rough, and I'm sorry about that. There are two things contributing to this (one of which should be fixed in the coming weeks).
First, we use HTTP requests on input (with delay for saving content). This is much slower than just using WebSockets behind the scenes. We'll be fixing that very soon.
Second, any network requests must connect to our coediting service. We are in the process of improving the distribution of that service to speed things up. Stay tuned!
Aleksandr Ladenko
Justin Hunter: Hello, Justin Hunter.
Thank you for your response and the great news that work on this problem - is already underway!
We'll wait for news.
Bernd Homberg
Here in Germany we have also a delay on loading task and start writing. Performance is really not good. :-(