What is more resource intensive? storing or readin everytime

Question

If I have a user model and a sessions thingy, 1. Is it better to store an object of the user model in the sessions thingy and use that or 2. just store the ID of the user in sessions and create a new user model instance everytime I need user data.

In option 2 you'd query the db quite a lot I think but someone suggested that option 2 is less resource intensive and i'm not quite sure why since you'd be loading the user data out of the db on almost every single page.

A sessions variable, something u can store it in – Mazzy Nov 27 '13 at 21:54 — Mazzy, Nov 27 '13 at 21:54
Why don't you try measuring both to see – Mark Baker Nov 27 '13 at 21:58 — Mark Baker, Nov 27 '13 at 21:58

score 1 · Accepted Answer · edited May 23 '17 at 11:56

1

If it's user-specific and you need it very often, it is perfectly reasonable to store it in session. Make sure the object stays small though.
Don't use session as a cache.

Have a look at these similar questions as well :

PHP: Storing 'objects' inside the $_SESSION

Store it in Session or Query DB each page load?

edited May 23 '17 at 11:56

Community

1
1

answered Nov 27 '13 at 22:28

Matthew

10,988
11
54
69

What is more resource intensive? storing or readin everytime

1 Answers1