Greetings, I'm here with a side project that is focused on providing a user-friendly search with a few other features, and I wanted to get some feedback on this before potentially bringing this up to Jayce who owns Divinelegy.
As a side note, I am not concerned about the aesthetics of this site right now. The design for the site can be improved later.
Link to Pad Search. Tentative unoriginal title for the time being.
Divinelegy
Not mobile friendly
Results are displayed under packs, then single files
Table could be improved
Pad Search
Search by BPM
LOADING TIMES
Some comparisons, Uncached (first time loading):
Regular 2G (250 Kbps 300ms RTT)
- Pad Search: 15 seconds
- Divinelegy: 49 seconds
Regular 4G (4 Mbps 20ms RTT)
- Pad Search: 2.25 seconds
- Divinelegy: 12.5 seconds
WiFi (30 Mbps 2ms RTT)
- Pad Search: 1.45 seconds
- Divinelegy: 9 seconds
Cached comparison:
WiFi (30 Mbps 2ms RTT)
- Pad Search: 1 second
- Divinelegy: 2.5 seconds
From this data it looks like Divinelegy tries to reload the simfile data every time the user visits the site, resulting in slow loading times -- especially when loading everything at once. Pad Search uses node.js, which has the behavior of storing the data in memory which doesn't require the user to reload it upon visiting the page so the web page can load faster. The searches are also a lot more lightweight, although could definitely be improved (an advanced search can be implemented, but for now this is just the original concept).
As a side note, I am not concerned about the aesthetics of this site right now. The design for the site can be improved later.
Link to Pad Search. Tentative unoriginal title for the time being.
Divinelegy
Not mobile friendly
Results are displayed under packs, then single files
Table could be improved
Pad Search
Search by BPM
LOADING TIMES
Some comparisons, Uncached (first time loading):
Regular 2G (250 Kbps 300ms RTT)
- Pad Search: 15 seconds
- Divinelegy: 49 seconds
Regular 4G (4 Mbps 20ms RTT)
- Pad Search: 2.25 seconds
- Divinelegy: 12.5 seconds
WiFi (30 Mbps 2ms RTT)
- Pad Search: 1.45 seconds
- Divinelegy: 9 seconds
Cached comparison:
WiFi (30 Mbps 2ms RTT)
- Pad Search: 1 second
- Divinelegy: 2.5 seconds
From this data it looks like Divinelegy tries to reload the simfile data every time the user visits the site, resulting in slow loading times -- especially when loading everything at once. Pad Search uses node.js, which has the behavior of storing the data in memory which doesn't require the user to reload it upon visiting the page so the web page can load faster. The searches are also a lot more lightweight, although could definitely be improved (an advanced search can be implemented, but for now this is just the original concept).


Comment