Calling PlayerPrefs.GetInt/GetFloat every update bad for performance?

Archived Forums Questions & Answers
1

Just curious, is using PlayerPrefs once per update frowned upon? I’m currently using it to synchronize values between classes (i.e. PlayerPrefs.GetInt(“Health”)). If it’s bad for performance I can switch to something else like a signleton or just a static int value instead. I use playerprefs a lot for many different things and now I’m starting to think that maybe it would be hurting performance and not the best thing to use for what I want…

Using PlayerPrefs for something else than saving and restoring value between sessions sounds wrong to me. I'd avoid it and stick to singleton/static variables, cache the manager script or anything else, really.

 –

1 Answer

1
2

You’d be hitting the disk like 100 times/second for no good reason. Your other options are better.