Hi
Two observations - you may or may not take them into acocunt, it's experience we had with caching:
Caching is always a way of getting a bit more performance, but because of caching we ran into some ugly problems which crashed Notes. Besides, caching works pretty bad for a browser, since whatever you do in web agents is lost after the page gets back to the browser. Typical example: you open a document in a foreign database for writing config info into it, then you delete the foreign database. Notes (6.0 at least) will crash upon a retry to access the document from the deleted database, instead of nicely generating a catcheable error. And the like.
We also gave up profile documents for configuration options, because you cannot use a similar mechanism for editing the config info in the browser and in the client, since profile documents cannot be edited in a browser. We came to the conclusion there's not much of a difference between using profile and normal documents for storing config info - you can easily create a convenient mechanism for extracting config info from both LS and from formula from normal documents, so there's not much mor ease when working with profile docs.
br,
flj