How is the access speed of registry values compared to configmanagers user.config?

Question

0.00/5 (No votes)

See more:

I already googled it, but currently have not found an answer.

I'm thinking about storing application settings. So I can use the .NET ConfigurationManager to use a user.config in %AppData%. One possible way is to store the information in a registry key.

But when comparing them both how is the speed? I'm guessing the user.config is slower because each request has to open, read and close the file. And the registry is running completely in the memory by launching Windows.

Maybe anyone knows more?

What I have tried:

I already searched via Google, but found nothing.

Posted 21-Jan-22 8:27am

Sascha Manns

Updated 21-Jan-22 9:45am

Sean Ewington

v2

Add a Solution

Comments

PIEBALDconsult 21-Jan-22 14:34pm

I generally use XML files in either
APPDATA -- User-specific
or
ProgramData -- Global to all users
The Registry is evil; don't use it.

Sascha Manns 21-Jan-22 14:38pm

Can you tell me more? What are the difficulties with registry?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2022-01-21T09:45:00

A major problem with the Registry is portability. The Registry is specific to Windows only. That means you cannot use it if you port your code over to other platforms, like phones.

If all you're doing is storing a small list of settings, speed isn't a concern at all. Reading/writing to file or registry is going to be negligible.

Oh, and the Registry isn't completely "in memory". It has to be stored somewhere or else the entire thing will disappear when you shutdown Windows. It's stored in files in the system and user profiles.

Today, the Registry is basically being discouraged because of abuse, portability, bloat, backup and restore difficulties, and fixing possible corruption.