track timings for UI operations
Some users complain that operations are slow and it is difficult to reproduce that.
We could add measuring points to some UI operations and gather statistics about the timings. This would give an objective value we can refer to and that can serve as a reference for future improvements.
The data should contain information about:
- user id
- machine id
- event id (operation measured or other info, like eclipse session start)
- event timestamp (to check for possible global condition affecting several users)
- event duration (or other event data)
It would be nice if we could gather this more or less in real time (in controlled environments).
We could add measuring points to some UI operations and gather statistics about the timings. This would give an objective value we can refer to and that can serve as a reference for future improvements.
The data should contain information about:
- user id
- machine id
- event id (operation measured or other info, like eclipse session start)
- event timestamp (to check for possible global condition affecting several users)
- event duration (or other event data)
It would be nice if we could gather this more or less in real time (in controlled environments).
Leave a comment
on 2013-05-28 10:44 *
By Vlad Dumitrescu
Description changed from Some users complain that op... to Some users complain that op...
Description changed from Some users complain that op... to Some users complain that op...
on 2013-05-28 10:44 *
By Vlad Dumitrescu
Estimate changed from Small to Large
Sum of child estimates changed from 1.0 to 7.0
Estimate changed from Small to Large
Sum of child estimates changed from 1.0 to 7.0
on 2013-05-30 12:55 *
By Vlad Dumitrescu
Shade tickets changed from X to 21564
Shade tickets changed from X to 21564
on 2013-05-30 13:01 *
By Vlad Dumitrescu
The core functionality is implemented, but adding trace calls to all interesting places is a problem. We would like an easy and simple way to mark a method as "traceable".
The simplest way to do that would be to go forward with the ErlangEngine and then only the methods on the engine facade need to be traced. But there's a lot to do to get an engine facade....
The simplest way to do that would be to go forward with the ErlangEngine and then only the methods on the engine facade need to be traced. But there's a lot to do to get an engine facade....
on 2013-07-02 17:43 *
By Vlad Dumitrescu
Milestone changed from backlog to v1.0
Milestone changed from backlog to v1.0
on 2015-09-15 14:12 *
By Vlad Dumitrescu
Category changed from Bug to New feature
Found in version changed from 0.23 to -none-
Category changed from Bug to New feature
Found in version changed from 0.23 to -none-
on 2017-11-08 17:20 *
By Vlad Dumitrescu
Status changed from New to Invalid
Status changed from New to Invalid