-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discover random photos #17
base: preview
Are you sure you want to change the base?
Conversation
2ca690d
to
d0b1b3e
Compare
Hello @kvalev Wondering if you've noticed performance issues with pages |
Hey @rickysarraf, no, not really, but to be honest I am not using them very often. |
@kvalev I must have cherry-picked the MR for The performance problem is with both, I noticed the problem right from the beginning when it wants to render the page. Compared to pages like There isn't any large set of data I think. For example, I'm not very savvy on web technologies but if you point me to what all I should do to help provide you with more information, I'll be glad to do that. |
I went and tried to do some checks. First of all, sorry, the issue is only with I used Chromium to do my first debugging. Thankfully, Chromium has a |
Firefox too has some Developer Tools. And I realized that Firefox is facing the problem in Desktop View mode too. Here's an interesting finding on the Firefox side.
|
Thanks a bunch for the pointers! I will taka a look ASAP. It is very weird that this happens even when there are only 12 photos. I tested in the past few days and I had significantly more than 12, and the UI was quite snappy. I tried it both with Firefox as well as the chrome-based mobile app and no issues so far. Now that you posted your benchmarks, I will check mine and will let you know what I figured out. |
[Discover on this day] I have noticed that when I open up the [On this day] tab that the pictures aren't in chronological order. They're going all through the years Example: 2012, 2019, 2016, 2015 Where I would expect the oldest one to be at the top and then reaching up to the latest. |
I never paid attention to the sorting order. But now that you've reported @fly-man- I have picked up this MR in my local test build. @kvalev The order on my machine, is still from |
Thanks @rickysarraf for testing! Do you see any performance problems or improvements? Re sorting - I personally think that from newest to oldest is a more logical sort order (hence the change in the PR), but if there is a strong pull for the other way around I can also make the order configurable. |
I did not encounter any performance issues. But that is because I don't have enough data to render a longer list for
I agree. I think it is logical to have the newest first, as the default. Having it configurable can make it much better. |
By the way, @kvalev, The initial performance issues that I had faced, for which I reported this issue, is now resolved. My guess is that the performance enhancements that Heiko Mathes added, play a very important role here. |
I think there isn't much need for this feature, as it is possible to sort by |
No description provided.