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

Display of mapping list is very slow when there are many fields (250) #1215

Closed
RDmitchell opened this issue Jan 20, 2017 · 5 comments
Closed

Comments

@RDmitchell
Copy link

RDmitchell commented Jan 20, 2017

When importing a Portfolio Manager file that has a lot of fields (250?) the program takes over a minute to display values from the pulldown list in the Mapping field, or even let you type in the field.

SHA: 37a30b0
instance: seeddemostaging
Org: LBNL 430 test account
Folder with sample file
https://drive.google.com/open?id=0B3fTKpZ9Dx7LSmJYMkU0Q3ptN0U

@RDmitchell
Copy link
Author

This is really excruciating even when there aren't very many records but there are lot of fields. May not be able to wait until the V 2.1 Release for this -- might need to do an intermediate update before that.

@RDmitchell
Copy link
Author

This slowness also applies to the Mapping Review screen. It is hard to know what the program is doing because you click on the Save Mappings and nothing happens. Maybe the program is still on filtered_mapping_results, but it's really hard to figure out. One has to be very patient. I have tested this on a file with just 9 records, and another with 163 records, which I can provide for testing.

@RDmitchell
Copy link
Author

I am doing this on staging with one of the user PM files, 58 records, 240 (approx) fields, and when I click on the Save Mappings button, here is what the program is doing
image

Eventually the Confirm Mappings and start matching dialog box shows up (probably at least 5 minutes to get there, probably more),

During this time I have the Developer Tools open (chrome) and it is very unresponsive during much of this -- takes forever to even resize the developer tools interface.

Because the interface is so slow, and you can't tell what's going on, I clicked multiple times on Save Mapping, and the program at some point says that the matching is already done, and then tries to do it again.

I would say the program is barely useable for this functionality, which is one of the primarly tasks that users need to do, so we need to work on performance enhancements for this as soon as possible.


On a normal file (the sample PM file with 512 records, but not very many fields, the program only makes the Organization call once with GET and once with PUT and then is able to move on to start_system_matching
image

@RDmitchell
Copy link
Author

Folders with sample files
https://drive.google.com/open?id=0B3fTKpZ9Dx7LSmJYMkU0Q3ptN0U
and from issues #1275
approx 250 fields, 58 records
https://drive.google.com/open?id=0B3fTKpZ9Dx7LLXVXdEUzem04aUU

axelstudios added a commit that referenced this issue Apr 7, 2017
…regard to typeahead/autocomplete/duplicate checking #1215
@RDmitchell
Copy link
Author

instance: dev1
SHA: fa46f28
Fixed, closing.

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

No branches or pull requests

1 participant