Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow display of data #1105

Closed
RDmitchell opened this issue Oct 28, 2016 · 1 comment
Closed

Slow display of data #1105

RDmitchell opened this issue Oct 28, 2016 · 1 comment
Assignees
Labels

Comments

@RDmitchell
Copy link

On a call with the City of Philadelphia last week, the performance of the program in terms of getting data from the server (ie, displaying the data in the View by Property and View by Tax Lot) was excruciatingly slow.

The user was using a computer with Windows 10 and the Edge browser on a reasonably decent internet connection.

I tested the performance of getting this data for this organization, on the same instance (the v2 production server) for the following situations and didn't experience the problem:

  • Laptop with Windows 10 and Edge using wireless internet connection at LBNL -- performance was as expected -- 13-15 seconds for the data to display
  • Desktop at home with Windows 7 and Chrome using a moderately decent wireless connection -- performance was as expected -- 13-15 seconds for the data to display

So it seems that it is probably not the window OS or the browser.

I have requested that the user talk to her IT department to see if they can figure out what the data bottleneck might be. Depending on their answer we may want to look into how we could improve the performance.

Under the current circumstances, it is not really possible for the user to use the software. So we need to determine if it is something that can be fixed on their IT side, or if it something that we need to do in our software.

Would be good to get this resolved by the end of November 2016 if possible.

@RDmitchell
Copy link
Author

On a webinar yesterday with Philadelphia she commented on the fact that the program seemed to be much faster in moving between tabs, etc. I know that several improvements have been made lately, and the users seem to be picking up on them, so I am going to close this issue. We can open issues later for specific areas of poor performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants