[eluser]GreGre[/eluser]
I have runned the profiler in order to check for optimisation possibilities and found out that the session class makes up to 10 or more queries per pageview.
Since we are dealing width OOP I was sure the session class makes one read and one write to the database. As I can see, the session class updates the database everytime I use set_userdata or set_flashdata in my routine.
I think this should be optimized.
I suggest to use set_userdata only once - for example with a hook at the end (post controller) - and write an intermediate library that will store and update userdata in a object during runtime.
