BUG: Poor performance when saving client-side qwd demos

[meag]

ezQuake version: All

OS/device including version: All

Describe the bug Playing while recording client-side demos (.qwd) can produce microstutters.

lordlame: saving when his hard drive has less than 10% space left Nidweyr: saving on his new hard drive, period

Looking at the code, individual messages are written out in parts (sometimes byte by byte). There is a democache command-line option which helps, but it should be writing per-packet at least. Bonus points for moving to another thread.

To Reproduce Record a .qwd (/match_autorecord or manually with /recordqwd)

Expected behavior Smoother performance when recording demos, this isn't 1996

[Matrix-QW]

Possible to record demos in memory instead? This would avoid SSD disk wear out.

[HangTimeQW]

@Matrix-QW that is what democache does iirc

[Matrix-QW]

I don't think the cmdline -democache is working properly or at all. It still writes matchinfo\demos\temp\_!_temp_!_.qwd when match starts. When match ends, it should only write to disk if match_auto_record 2 is set or with match_save. Also, would be possible to set democache as a variable instead of cmdline?