Remembering parsed data between requests

[Desdinova]

My current architecture parses an ini file to an array and does some regex matching on that. With each request, this ini file is parsed again and again. I'm not sure, but this sounds like a potential performance issue.

I thought maybe it's a good idea to put the parsed ini in the session, but I'm not sure if that's a good option performance wise.

It's not just with this ini file, it's more often that I need data in a few requests. In terms of performance, what would you say is the best way of remembering this data between requests, instead of fetching it again?

[laserlight]

As long as you are not parsing the file multiple times per request, you could be okay. Storing the array that is the result of the parsing in a session may or may not help since the session may be stored in a file and thus parsed (i.e., unserialised) to load the session's contents.

You could also try storing in a database instead, with the name column indexed. However, you say you do "some regex matching" but you didn't specify what exactly you were matching against.