Browser Memory Usage of Large Exports on Old Version

[Shadowmech88]

Browser Memory Usage of Large Exports on Old Version

[slatinsky]

There is a way - move out some exports from /exports folder

v2 client-server rewrite already fixed this issue - client in this version requests only required data from the server

[Shadowmech88]

move out some exports from /exports folder

What if it's just one single guild with one single channel that simply has an enormous amount (millions) of messages? There'd be nothing to move out of the folder.
Also I tried a partitioned export (and those partitions of that single channel of that single guild are the only things in the exports folder) and I still have the same issue. The computer absolutely has enough RAM to handle it, but are there any browsers/programs capable of viewing the local server and allocating that much RAM to a single tab?

client in this version requests only required data from the server

Out of curiosity, does v2 still work this way when accessing the running instance via a web browser in the case of the Docker version? Or would I see similar OOM errors with even a recent release of the Docker version of DCEF?

[slatinsky]

Out of curiosity, does v2 still work this way when accessing the running instance via a web browser in the case of the Docker version? Or would I see similar OOM errors with even a recent release of the Docker version of DCEF?

v2 send to the client only message ids of the channel and only messages in the viewport are requested. That means that you can reach out of memory errors at some point, but you would need really really really large channel to reach that (unlikely).

[slatinsky]

Closing as won't fix. Memory usage is better in the latest version of frontend and it is not worth it to backport the change