Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimized / Faster recording speeds? #235

Closed
Dechno1337 opened this issue Oct 4, 2019 · 3 comments
Closed

Optimized / Faster recording speeds? #235

Dechno1337 opened this issue Oct 4, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@Dechno1337
Copy link
Member

Dechno1337 commented Oct 4, 2019

Is it possible to optimize the way the images (and/or videos) are being written on the drive in order to make use of the full capabilities of the drive?

A drive is the fastest when reading or writing in a sequential order + making use of many "channels" (queue depths) on the drive controller, and using more CPU threads, as far as I understand it. I don't know what the limitations are in the Source engine, but would it be possible to change (increase) compared to what is being used now?

I think the most common applications can use up to ~8 queue depths, but most modern SSDs can handle up to 32 or possibly more. Is this something that can be exploited at all, or is there a hard engine cap?

@Dechno1337 Dechno1337 added the enhancement New feature or request label Oct 4, 2019
@dtugend
Copy link
Member

dtugend commented Oct 6, 2019

Currently HLAE only writes out the images on the drawing thread, meaning 1 image at a time.

I wouldn't expect writing multiple images being notably faster on Windows 10, since it uses operating system file functions to write them, but I don't know to be honest.

We would have to gather data / clues on this.

@Dechno1337
Copy link
Member Author

Not sure how relevant this is, or may shed some light on how data is sent through the system:
https://devblogs.microsoft.com/directx/directstorage-is-coming-to-pc/

@dtugend dtugend removed this from the v3.2 milestone Feb 13, 2021
@dtugend dtugend closed this as completed Feb 13, 2021
@advancedfx advancedfx locked and limited conversation to collaborators Feb 13, 2021
@advancedfx advancedfx unlocked this conversation Jul 5, 2021
@dtugend dtugend reopened this Jul 5, 2021
@dtugend dtugend closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2022
@dtugend dtugend reopened this Oct 9, 2022
@dtugend dtugend self-assigned this Dec 3, 2022
@dtugend
Copy link
Member

dtugend commented Dec 3, 2022

Merging this into #295, thus closing.

@dtugend dtugend closed this as completed Dec 3, 2022
@dtugend dtugend removed their assignment Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants