Channel page claim caching / other optimizations #1255

New issue

Closed

opened 2018-04-03 00:30:45 +02:00 by tzarebczan · 2 comments

tzarebczan commented

2018-04-03 00:30:45 +02:00

(Migrated from github.com)

The Issue

When you go into a channel page likelbry://@lumbridgecity, the page starts fetching content which takes a bit of time. If you enter a claim or go to another page, and then go back, it re-fetches content again making this a slow process. We should try to add some type of caching to reduce the subsequent load times. Have to take into account new/updated claims as well.

Update: The current process also runs claim_list_by_channel on the first page which returns all the claim data. It then proceeds to run a resolve on each of the claims (if they have not been visited in the current session). The resolve should not be needed as the prior call has all claim data returned. If we do need to run a resolve, we should batch it.

Expected Behaviour

Faster subsequent load times

Actual Behaviour

Reload every page as if it were the first time seeing it

System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

## The Issue When you go into a channel page likelbry://@lumbridgecity, the page starts fetching content which takes a bit of time. If you enter a claim or go to another page, and then go back, it re-fetches content again making this a slow process. We should try to add some type of caching to reduce the subsequent load times. Have to take into account new/updated claims as well. Update: The current process also runs claim_list_by_channel on the first page which returns all the claim data. It then proceeds to run a resolve on each of the claims (if they have not been visited in the current session). The resolve should not be needed as the prior call has all claim data returned. If we do need to run a resolve, we should batch it. ### Expected Behaviour Faster subsequent load times ### Actual Behaviour Reload every page as if it were the first time seeing it ### Suggested Solutions Employ caching strategy ## System Configuration   - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else  ## Screenshots

tzarebczan commented

2018-07-17 16:26:12 +02:00

(Migrated from github.com)

Reopening to address the last issue (cc: @daovist )
The current process also runs claim_list_by_channel on the first page which returns all the claim data. It then proceeds to run a resolve on each of the claims (if they have not been visited in the current session). The resolve should not be needed as the prior call has all claim data returned. If we do need to run a resolve, we should batch it.

Reopening to address the last issue (cc: @daovist ) The current process also runs claim_list_by_channel on the first page which returns all the claim data. It then proceeds to run a resolve on each of the claims (if they have not been visited in the current session). The resolve should not be needed as the prior call has all claim data returned. If we do need to run a resolve, we should batch it.

tzarebczan commented

2018-07-23 21:02:03 +02:00

(Migrated from github.com)

Closed by https://github.com/lbryio/lbry-redux/pull/60