Please revise the way the list of solutions is retrieved and transmitted because it is annoyingly slow.
Have you considered latency in transmissions (lower is better) ? compression of the http data (stronger is better) ? Number of interactions needed for the transfer (lower is better) ? Caching of the list if you are only interested in a local solution ?
Changing tracks retrieves this list, but does nothing with it, trying to open a solution in the new track then re-retrieves the list (48 seconds delay total).
All are possibilities for improvement.
Bump, this should one of your top priorities to solve as it is exceptionally annoying
bump Please fix this as it is EXTREMELY ANNOYING to have to wait every time you change a track, every time you load a LOCAL solution, every time you upload an Alphafold solution, for 24 seconds.
Have you implemented an index on the database you are retrieving the solution from ? One index on player number and one on puzzle should be the least you implemented as it is noticeable that the time it takes grows as the puzzle progresses and more solutions are uploaded and saved.
BP–can you provide me with steps to reproduce this bug? That would be very helpful!
@agcohn821 Use the client and generate a few new solutions, save them locally, upload a few to the AF window, upload a few as a share to yourself on the server and watch the delay grow. For the other bug that has been lingering regarding the big text in notes, (this one: https://fold.it/forum/bugs/unresolved-20221003-677257a5d4-win_x64-devprev-using-cut-and-paste-in-notes-slows-down-the-client-to-a-crawl ) place a few hundered Kb of text into a note (my daily workflow) and then try to open the various popup windows, like notes window, tracks window, objectives window and close them again, you will see the delays I'm talking about.
Hey BP - we are working to eliminate unnecessary calls to grab solutions from the server, which should help the delay in these situations. We actually aren't seeing these delays on our end, but we are going through the code manually looking for cases that might cause the symptoms you've described.
Thank you @jflat06 that would be great for a start.
