The only point of caching in any case is performance. There are bad
side-effects of caching, so performance must be more important than
other things (like possibility of stale cache, etc).
What I'm baffled by, and the only reason I responded, was the idea
that caching in the database is _faster_ than local caching on the app
server. Any time you do a database round trip you're talking about
serialization of data, network communication, and deserialization...
and all of that in both directions. Even a simple lookup where the
database has it cached will take a few milliseconds.
This really has nothing to do with OFBiz, it's all in the network and
hardware that this performance impact comes in. These are usually huge
factors in designing distributed systems.
So, I guess the point of my questions is how could remote caching ever
be faster than local caching? In other words, I was asking because I
must be misunderstanding something as this doesn't seem to make any
sense.
Not sure what you mean by "Oh my goodness. Not again." It's really not
that sensational, just basic computer stuff, really quite boring and
plain actually.
-David
On Apr 19, 2008, at 2:37 AM, Jonathon -- Improov wrote:
Oh my goodness. Not again. I thought someone else posted his tests
of retrieval speeds regarding this?
Call it what it is, and we'll always be alert to necessities for
change. Side note: No point telling everybody "it's all there, you
just can't find it", when they might have the ability to actually
confirm without doubt that parts of functionalities are not there.
I don't have time to write every reason there is for OFBiz's
caching, please. Of course it's good to be able to specifically
spell out to OFBiz which entities you want cached; RDBMS do not
always know (if at all) which entities should be cached more. The
designer of the software will know the usage pattern the software is
designed for. So how many points do I get for that answer? :) Sigh.
So would you mind listing all the reasons for OFBiz's caching of the
database entries? :) You designed it, I believe. You would know.
Thanks!
Jonathon
David E Jones wrote:
On Apr 19, 2008, at 2:04 AM, Jonathon -- Improov wrote:
Chris is right that dynamic view entities are exactly like view
entities. Both run through the same Entity Engine. Caching by
OFBiz is also good, though much slower than RDBMS-native caches;
Really? What would be the point of local caching on the app server
then? (hint: it definitely isn't for database independence)
Have you actually done tests on this to see what typical times look
like, even for a database running on the same machine?
-David
