Re^2: Caching files question

graff, by query I do not mean sql query. My files are not in DB, I do not use DB at all.
Yes, retrieving data from HD takes much more time than processing and again I know how to rearrange my code to retrieve it just once.
Yes my data fits RAM.
I just want to know if it's possible to do caching (besides OS caching) without rearranging the code.

Comment on Re^2: Caching files question

Replies are listed 'Best First'.
Re^3: Caching files question by graff (Chancellor) on Aug 17, 2008 at 13:27 UTC
I just want to know if it's possible to do caching (besides OS caching) without rearranging the code. Sorry... I wouldn't know how to answer that without seeing some of the code in question. Actually, I'm not sure what that question means, if you are trying to ask about something other than loading all the file data into RAM. Maybe BrowserUK has provided a relevant suggestion, if your existing code has "open()" statements scattered throughout that happen to be reopening the same files over and over. But if that is the case, perhaps going ahead with a suitable refactoring of the code would be time well spent. (Updated to adjust grammar and punctuation, and to add the following:) by query I do not mean sql query. I wasn't specifically referring only to sql queries either, but was including an RDB solution as a possible alternative (along with hash look-up, which does not involve sql but could be viewed as another type of query). You've left it unclear what "query" means in your app, but perhaps that's not relevant. My files are not in DB, I do not use DB at all. And my point was: if your existing app is problematic in some way, you might want to consider using some sort of DB as an alternative for improving it.	[reply]

Replies are listed 'Best First'.

Re^3: Caching files question
by graff (Chancellor) on Aug 17, 2008 at 13:27 UTC

I just want to know if it's possible to do caching (besides OS caching) without rearranging the code.

Sorry... I wouldn't know how to answer that without seeing some of the code in question. Actually, I'm not sure what that question means, if you are trying to ask about something other than loading all the file data into RAM.

Maybe BrowserUK has provided a relevant suggestion, if your existing code has "open()" statements scattered throughout that happen to be reopening the same files over and over. But if that is the case, perhaps going ahead with a suitable refactoring of the code would be time well spent.

(Updated to adjust grammar and punctuation, and to add the following:)

by query I do not mean sql query.

I wasn't specifically referring only to sql queries either, but was including an RDB solution as a possible alternative (along with hash look-up, which does not involve sql but could be viewed as another type of query). You've left it unclear what "query" means in your app, but perhaps that's not relevant.

My files are not in DB, I do not use DB at all.

And my point was: if your existing app is problematic in some way, you might want to consider using some sort of DB as an alternative for improving it.

[reply]