speed of landing page

[hannesdatta]

hey @thierrylahaije - I resized the pic on the landing page, but the speed hasn't increased substantially. I believe there must be a database call that takes a very long time to load.

Can you check which one that is?

We can them devise a strategy for making that query faster (or, you can suggest one).

Curious to hear!

[thierrylahaije]

Hi Hannes,

I checked the speed of the queries at the homepage. At first when I check, the speed was about 1.24 seconds. I was able to increase the speed up to 0.02 seconds, an increase of approximately 98%. More details below (summary):

• Index: 1.24s -> 0.02 seconds = 98.39% increase in speed.
  • Recent tracks: 0.24s -> 0.01s
  • top_songs: 0.47s -> 0.0006s
  • Featured_artists: 0.0017s
  • recent_users: 0.42s > 0.00015s

[hannesdatta]

I checked, but it still seems buggy:

• the landing page takes 7-9 seconds on my mac to load.
• check screenshot of landing page: many songs ranked the same

(e.g., a bunch of 1s - while there should just be one...)

• Further, I noticed several of the users that were supposed to have listened to content actually didn't listen to anything during this week.

Finally, just out of curiosity: what's the reason you switched main.py to app.py, btw?

Good idea to have an index, but these issues still need to be resolved.

[thierrylahaije]

About these points:

• Speed issue: the speed has been checked and should be fast now. I made some adjustments to my own repository of the flask app on azure, which contains speed updates for the performance of the .html pages. Maybe your mac has difficulties receiving certain files from the cdn (bootstrap, font etcetera). These will be deferred in the new update to make sure that these are not render-blocking.
• The ranks were indeed incorrect. This was due to some misfunctioning in the query. This bug is fixed.
• It makes sense that some users have no plays in this week. The week (from 5th on) has just started. I ran the simulate.r script and i saw that the latest listening of user512 was on first of June, meaning the Flask App is displaying the data correctly.
• The main.py was changed to app.py for deployment reasons. Azure expects you to deliver the main flask file with the name app.py or application.py