Handle big request more gracefully about pkappa2 HOT 4 CLOSED

We could show a warning banner for streams larger X instead of the contents like "This is a large stream, do you want to render it?" which would help skipping through results without getting stuck on those large streams.

This wouldn't fix the original issue, but make it a more concious decision to view the large stream. It's probably better to download the pcap and view it locally for >MB streams.

from pkappa2.

I suspect this is rendering performance of the <span> around every byte for searching selections @schmop ?

from pkappa2.

We could think of serving the stream data in chunks with a "load more" button at the bottom?
When serving a 10mb stream of downloading a file, we might not need all of it at once from the start?
Or disable the selection markup for large streams?

from pkappa2.

When the massive usage of tags around every char in the stream results in oom, then the "load more" option will only defer it until you loaded the whole stream.
Maybe we need to redesign the "copy/search from stream data" functionality. Or worst case remove it

Nonetheless, pagination would be awesome. Infinite scroll even?

from pkappa2.