Re^3: Database or Storable?

How much of the total dataset is required by any given access to the web page?

If, for example, only the Math questions are required by any given load, consider splitting the Storable datset into 2 and only loading the required set once you know which is required. You'll need to do a directory lookup anyway, and if you can defer that lookup until you've acquired the information telling you which half you need, the page will load more quickly and you'll only need to load half the data when you do.

If there is a natural split that reduces the amount of data further, try that also.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^3: Database or Storable?

Replies are listed 'Best First'.
Re^4: Database or Storable? by Anonymous Monk on Mar 09, 2009 at 11:29 UTC
The questions themselves are stored in the database, and are only accessed when the user selects a practice. The Storable came about because I was thinking it could be used to store the total statistics - not holding any questions. I could get the totals from the database, using COUNT(*) for instance, but I was wondering whether it might be more efficient to get these values from a stored hash reference, instead of querying the database.	[reply]

Replies are listed 'Best First'.

Re^4: Database or Storable?
by Anonymous Monk on Mar 09, 2009 at 11:29 UTC

The questions themselves are stored in the database, and are only accessed when the user selects a practice. The Storable came about because I was thinking it could be used to store the total statistics - not holding any questions. I could get the totals from the database, using COUNT(*) for instance, but I was wondering whether it might be more efficient to get these values from a stored hash reference, instead of querying the database.

[reply]