Slow response time to mouse clicks

We are currently experiencing very slow response time to mouse clicks. This is most noticeable on the sprint whiteboard, where opening a task or clicking on the +/- buttons to change burned/remaining time almost always takes a few seconds.

Snooping traffic between the client and the server shows that it is not a server side issue - response time is consistently around 10ms. Most of the delay appears to be between the mouse click and the request being sent to the server.

We are predominantly using Chrome (Version 26.0.1410.64 m), but I've tried an old IE version as well and it doesn't seem to be any better.

Status

Bug is fixed for Release 0.26.2. Needs to be tested.

Comments

Thu, Apr 25, 2013, 10:16 by Mike Evans

I should have added, this is using the latest version of Kunagi - 0.24.4.

I collected Javascript CPU profile output across a single click of a plus button on the Burned field of one task. This shows that most time (about 85% of non-idle time) is being spent in the Th function, almost always when called from vwd (although it looks like there are some missing calls in the profile output as vwd only calls Th via uwd(), Ub() and Kgc()). The call tree above that point is a bit more varied.

Thu, Apr 25, 2013, 15:15 by Witek (SM,T)

Could you please provide some information on how many stories and how many tasks you have on the whiteboard? Thank you...

Thu, Apr 25, 2013, 15:28 by anonymous

We currently have 6 stories and 56 tasks on the whiteboard.

Mon, Apr 29, 2013, 15:37 by anonymous

Is there any news on this. We like Kunagi, but if we can't get the response time down we will have to look at alternatives which will be a nightmare given how much data we have in it.

Is it possible to get debug JS code so we can do some profiling/debugging on site?

Mon, Apr 29, 2013, 15:48 by Witek (SM,T)

All source code is available on GitHub: github.com/Kunagi/kunagi

If you could send me your kunagi-data directory, I would be able to reproduce your problems and perhaps create a solution. If you are ok with this, you can send it to wi@koczewski.de. I will delete everything of course.

Since we are working with Firefox, could you please check the performance with Firefox and tell us if it has same problems?

Mon, Apr 29, 2013, 16:28 by artjom (PO,T)

Also please note that Kunagi is developed with GWT, not JavaScript. Thus, JavaScript errors and debugging is often of little help.

Wed, Jul 31, 2013, 14:06 by anonymous

I have sent our kunagi-data directory to wi@kocxzewski.de as requested.

Thu, Aug 1, 2013, 08:13 by Witek (SM,T)

You have a typo in the email addres: It should be: wi@koczewski.de. I did not get your email.

Thu, Aug 1, 2013, 09:01 by anonymous

I think the email address was okay when I sent the file (I must just have mistyped here). I suspect the issue is the size of the email - even gzipped the tar file is 31MB, so it may be being thrown away somewhere. I've resent it, but let me know if you don't have it in a few hours and I'll see if I can find another way to get the file to you.

Fri, Aug 2, 2013, 13:29 by anonymous

Have you received the data?

Fri, Aug 2, 2013, 16:32 by Witek (SM,T)

nope :-(

Fri, Aug 23, 2013, 15:20 by anonymous

I believe you have the data now. Any update on the issue?

Wed, Sep 4, 2013, 17:29 by Witek (SM,T)

We are migrating to GWT 2.5. This could help. But I am on this one. Thank you for your input so far.

Sat, Dec 21, 2013, 21:47 by artjom (PO,T)

Is this issue solved with the current vesion of Kunagi?

Sun, Dec 22, 2013, 17:51 by anonymous

We've been using 0.24.5 for a month or two and it isn't really noticeably better. The response time from our server is still good, but there is always a delay (sometime of a second or two) between a mouse click and the request flowing to the server. It makes clicking on plus and minus buttons to adjust hours worked/remaining a pain as it's very easy to over shoot.

Wed, Jan 8, 2014, 08:38 by Witek (SM,T)

Please try the latest version 0.25. I have made some more changes to address this issue. Please give feedback. Thank you very much.

Post a comment



optional
optional