search

jingyuyao / elitetraderoutes

A database containing item trade information for the game Elite Dangerous
MIT License
1 stars 0 forks source link

Client side rendering #26

Open jingyuyao opened 9 years ago

jingyuyao commented 9 years ago

Server side rendering of large dataset is eating up the cpu. This might be caused by either the sql queries or django's template system.

If the cause is django's template system, we should consider separating the data framework from front-end. We could separate the project in two and use two virtual servers to host them.

Solving #23 will be a good gauge on how difficult implementing this will be.

jingyuyao commented 9 years ago

From 00f7ac6, it doesn't seem that difficult to do full client side rendering. At worst we have to port every single template into its own js function. However, doing so will break the idea of rendering initial data server side and manipulating data client side. As with #23, I think js could be used to break down getting a huge dataset in one request but it should not be used as the sole method of getting data.

Data mining into the performance of either option is required to provide a final verdict.

jingyuyao commented 9 years ago

After #32 full client side render is now a real possibility. However, there is not enough real incentive for the switch. Right now normal full page load finishes under ~500ms and ajax calls is under ~50ms.