powered by Jive Software

Performance question about storing additional information

I have some additional information that I need to store about each user. The information gets refreshed every time they log in. I am looking at either storing it in a separate database table or as part of the session object. Every message that the user sends needs to be checked against the additional information. Which would be the better option for storing data based on the amount of times it would have to be referenced?


Your question is actually two questions:

  1. Storage - if this data needs to be persistent, store it in your own databse or simply add a table to the Wildfire database and enjoy some features like connection pooling with no extra effort.

  2. Using the data - once you access the data from the database, keep it cached in memory/session until the next time you need to read a fresh copy from the database.