Improve performance when going back to index from show

[kuatroka]

I've implemented a flop table with search, pagination and sort. All works smoothly and now I'd like to improve performance in the case when I go from individual record back to the listing. Here is the flow:
1 - User searches or flips through the table entries.
2 - When the right entry is found , user clicks on the row and it takes the user to the individual page for that row. (this is very fast)
3 - After reviewing the individual page for that row, the use click button "back to the list" and is taken to the initial table from the step 1. (this steps takes a lot longer )

Going from the list to the entry - 1us, but back. - 850us

The question, how can I improve the step 3? Maybe some setting exists or built-in cache option or tracking the very first table view? See the gif. Thanks

[woylie]

That's more of a LiveView question than a Flop question. Flop does not have built-in caching capabilities. If index and show are in the same LiveView, the items should still be assigned to the socket when you patch back to index. You could check whether you already have items for the given parameters assigned to the socket in handle_params and only fetch them from the DB if necessary.

[kuatroka]

I have index and show in separate liveviews, (generated with the standard Phoenix generators). I'll check this one out. Thanks.