search

StatsHelix / HeatmapWebsite

The sourcecode of
http://demo.ehvag.de
2 stars 0 forks source link

Prerender all the things #21

Closed main-- closed 9 years ago

main-- commented 9 years ago

so you don't need 1337GB of RAM to view some demos

moritzuehling commented 9 years ago

How will prerendering things will help? You need the raw data if you want individual selection to be possible. I think it'd be easier to just send the raw data, and let the client render it to save ram.

Disadvantage: Performance.

main-- commented 9 years ago

Prerender literally everything, so all the client has to do is display a single image. Or maybe find the right balance between stored images on the server, on-the-fly server-rendered images and clientside rendering.

Because right now, client performance is abysmal, even user feedback says that.

moritzuehling commented 9 years ago

Maybe we should go away from JS and use sth. Ylike MonoGame...?

Am 2. November 2014 00:53:16 schrieb "main()" notifications@github.com:

Prerender literally everything, so all the client has to do is display a single image. Or maybe find the right balance between stored images on the server, on-the-fly server-rendered images and clientside rendering.

Because right now, client performance is abysmal, even user feedback says that.

Reply to this email directly or view it on GitHub: https://github.com/moritzuehling/DemoInfo/issues/21#issuecomment-61388351

main-- commented 9 years ago

JS is definitely not the bottleneck, see Unreal Engine.

main-- commented 9 years ago

To be honest, we shouldn't even have to prerender. Unreal Engine runs ezpz, our little heatmap magic is nothing compared to that.

moritzuehling commented 9 years ago

Fixed all slow stuff by simply just not using images.