this post was submitted on 01 Sep 2024
31 points (100.0% liked)

Learn Programming

1631 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

For context, I am trying to do a save system for a game.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 2 months ago

Depends, are you using raw os APIs?

If so stop it and use a library. A library will do all the necessary checks anyways, atomically. And you need to handle API errors anyways. So checking ahead of time just would be a waste of time.

But in the end it's irrelevant. This all seems like premature optimization at best and optimizing the wrong thing at worst. You shouldn't need to open thousands of files a second to save a game and if you don't then the cost of all this checking is essentially zero.

And if you are actually bound by the speed of opening files then you should investigate ways to open fewer files (or not closing files that you know will be needed later).