Jump to content

Retrieval of existing time sheet entries - response time


Recommended Posts

@AlexTumber

Users are reporting that the response time of time sheet manager to display the timesheet entries when changing date or entering new activities using the right hand panel is a lot slower to populate the existing entries.

Does there need to be a re-index done to after installing the update?

Cheers

Martyn

Link to post
Share on other sites

@AlexTumber

Just to add to this, I am seeing some weird behaviour where the timesheet for a day will sometime populate and then and other time will not. It is almost like the request is timing out so it does not display any entries, when I know there are some.

Happy to demonstrate if that helps.

Cheers

Martyn

Link to post
Share on other sites
  • 7 months later...

@AlexTumber

We are seeing delays again in the retrieval of time sheet values on our instance. When moving from day to day it can take a minimum of 30 seconds, nearer a minute when all users are on the system.

Looking at the admin tool there does not appear to be a specific option for re-indexing the Timesheet Manger application.

We have over 330K records in our h_timesheet_values table but do not know how this compares to other users of the application.

Looking at the Entity Viewer, there are separate indexes on h_member and h_time, but there is no compound index for them both, which I would presume is what the where clause element of the query when accessing the timesheet uses. 

Cheers

Martyn

Link to post
Share on other sites
  • 2 weeks later...

@Martyn Houghton thanks. We are currently working on a new update to timesheet manager that should fix bugs and improve performance. It's being trialled on our beta system currently so it hopefully won't be too much longer before it makes its way to live.

Alex

Link to post
Share on other sites
  • 1 month later...

@AlexTumber

Appreciate the a release of Time Sheet Manager is imminent , but can you clarify if the performance changes have been tested on a large volume set of data like our and confirmed to resolve the Server Error timeout issue, as this is becoming quite frustrating for our users. This is especially true for our 1st Tier team who will deal a significant volume of time sheet entries on different requests as they deal with logging and updating requests from email and the customer portal.

Our 1st Tier team are struggling to be able to retrieve their time sheet details for a day without the server error being reported.

Cheers

Martyn

Link to post
Share on other sites

@Martyn Houghton yes the performance enhancements have been tested on large datasets and the workload has also been split down into multiple api's which helps to make things like the retrieval of just the list of timesheet values even faster. There are now 3 separate api's for getting the timesheet values, the charts and the total time lists which can all run asynchronously and independent of each other.

Alex

  • Like 1
Link to post
Share on other sites
  • 3 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...