These are chat archives for biojs/biojs

14th
Apr 2018
Rohit Gupta
@r0hit-gupta
Apr 14 2018 00:32
@Megh-Thakkar the server is up and running.
Sarthak Sehgal
@sarthak-sehgal
Apr 14 2018 05:05
rohitgupta1.png
rohitgupta2.png
Hey @r0hit-gupta, here's the response which I got.
Though, I'm a bit confused. Is this data only for the search bar or for each component's separate page?
Rohit Gupta
@r0hit-gupta
Apr 14 2018 05:09
Th
This is for the homepage.
Sarthak Sehgal
@sarthak-sehgal
Apr 14 2018 05:12
But the home page only contains top 3 components of 3 categories, right? Serving all the components would take unnecessarily more time. As @rowlandm pointed out, we'll have to go for data slicing.
When Megh and I were making the prototype, the 9 components were loading within 100ms as far as I remember. I'll just test that once again.
Try having only 9 components. It would increrase the speed and efficiency!
Rohit Gupta
@r0hit-gupta
Apr 14 2018 05:14
Sorry. Its for the components page. The page where all the components would be listed.
Sarthak Sehgal
@sarthak-sehgal
Apr 14 2018 05:17
Again, as @rowlandm pointed out, that page should ideally contain only the top 10 components. I think it's not about the retrieval of data of 200 components which would take much time but it's rendering. Rendering of data of 200 components, displaying all the images, etc. would time.
I read somewhere that rendering of data dominates retrieval of data when talking in terms of speed (I'll try to find the source). So in my opinion, we should take up the MVP approach and display the top 10 components.
Alkesh Srivastava
@alkesh47
Apr 14 2018 06:10
@sarthak-sehgal The components are not getting rendered all at once. As discussed earlier with @r0hit-gupta , during the testing phase, we were only fetching the components but not rendering them all at once. Only few of them would get rendered and the rest would be lazy loaded on page scroll. That solved the rendering part of our problem.
Rohit Gupta
@r0hit-gupta
Apr 14 2018 06:58
Yes. As suggested by @alkesh47, components can be lazy loaded when required. Moreover, Vue.js is powerful enough to handle and render tons of data. A virtual list should be fine for us.
Alkesh Srivastava
@alkesh47
Apr 14 2018 11:55
Hi @all I just tried rendering the response from @r0hit-gupta 's API and the results are great. Even without lazy loading and infinite page scroll, all the components are getting rendered easily. Once lazy loading kicks in, everything would be a breeze.
Minifying the response from the backend has definitely sped things up on the frontend.
The prototype in the video is using Vue and as expected, Vue is easily able to render all the data.
Abhinavvisen
@abhinavvisen
Apr 14 2018 11:59
The response rate is really great.We don't have to worry about the backend data now.@alkes
Alkesh
Rohit Gupta
@r0hit-gupta
Apr 14 2018 12:38
@alkesh47 that looks blazingly fast. Great work. :+1:
Alkesh Srivastava
@alkesh47
Apr 14 2018 12:40
Thanks :smile:
Sarthak Sehgal
@sarthak-sehgal
Apr 14 2018 18:58
Hey @alkesh47, that looks great!
Have you tried it on a server?
Alkesh Srivastava
@alkesh47
Apr 14 2018 19:05
I did, but I was unable to fetch response from the API due to some network error. I guess that's due to the fact that's the API was being served using http and I was using https on the cloud. But the results should remain the same.
Rohit Gupta
@r0hit-gupta
Apr 14 2018 19:20
@alkesh47 let me know if you want https support. Will add it.
Alkesh Srivastava
@alkesh47
Apr 14 2018 19:22
Well it's working but it requires disabling mixed content blocking on the browser.
Rohit Gupta
@r0hit-gupta
Apr 14 2018 19:23
Ah alright. Will add https support to prevent any further issues.
Alkesh Srivastava
@alkesh47
Apr 14 2018 19:24
Thanks a ton, that helps a lot :+1:
Alkesh Srivastava
@alkesh47
Apr 14 2018 19:36
Hi @all I have made minor performance tweaks, you can check the response now at https://flowerhorn-vue.herokuapp.com/#/
rowlandm
@rowlandm
Apr 14 2018 20:44
Nice work discussing this everyone!
Alkesh Srivastava
@alkesh47
Apr 14 2018 21:16
Thanks @rowlandm