Too may api calls at startup #63
Labels
No Label
Difficulty - Beginner friendly
Difficulty = Easy
Difficulty = Hard
Difficulty = Medium
Priority = CRITICAL
Priority = High
Priority = Low
Priority = Normal
Priority = Some day
Status - Fixed somewhere else
Status - No details provided
Status = Can't fix
Status = Duplicate
Status = Help wanted
Status = Invalid
Status = Need more details
Status = Taken
Status = Wontfix
Type - Selfoss works like this
Type = Bug
Type = Chore
Type = Enhancement
Type = Feature
Type = Question
Type = SELFOSS API ISSUE
Type = Tools
Type = UX/Design
Up For Grabs
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Louvorg/ReaderForSelfoss-multiplatform#63
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As I said in #59 the application appears to make too many api calls.
I tested this on the latest commit (
da71de6806
)When starting up the application, 5 api calls to /items are made.
The first 3 are made with the parameter unread and the other two with the parameters all and starred.
I'll point out that all offline settings are disabled, thus no call should be made for all or starred.
After the first three calls to unread the list of articles loads up in the application, the other two calls are made after the application correctly loaded the articles and shows them.
This might be the reason why the new application feels slower to start up compared to the old one.
Ideally, only one api call to unread should be performed at startup.
@davidoskky can you please try the
enhancement/too-many-calls
branch ?I didn't see a lot of improvement compared to the android version.
Retrofit seems to be super fast compared to ktor.
Also, note that the default article to fetch was 200. I changed it to 20, and things are quicker.
Yes, in your branch it is working correctly and only one call is made at startup.
It does feel a little bit quicker, but that's probably due to the number of fetched articles.
I'm not testing the loading time extensively since I'm not sure how I would go about doing that reliably.