pages without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code they are writing.
In theory is it possible to write an entity cache that can be used
100
example of this is the goal
to be
able
to render ecommerce catalog and product pages without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code they are writing
ecommerce catalog and product pages without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code they are writing.
In theory is it possible to write an entity
to keep
frequently used values/records closer to the code that uses them, ie
in the
application server. One real world example of this is the goal to be
able
to render ecommerce catalog and product pages without hitting the
database.
Over time the entity caching was made more complex to handle more
real world example of this is the goal to be
able
to render ecommerce catalog and product pages without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code
used values/records closer to the code that uses
them, ie
in the
application server. One real world example of this is the goal
to be
able
to render ecommerce catalog and product pages without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios
the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code they are writing.
In theory is it possible to write an entity cache that can be used
100%
of the time? IMO
of this is the goal to be able
to render ecommerce catalog and product pages without hitting the database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if caching
is appropriate for the code they are writing.
In theory
Crum adrian.c...@sandglass-software.com
To: dev@ofbiz.apache.org
Sent: Saturday, 21 March, 2015 10:39:09 AM
Subject: Re: Entity Caching
Thanks for the info David! I agree 100% with everything you said.
There may be some misunderstanding about my advice. I suggested that
caching should
quoteThe decision to cache or not should be made by a sysadmin/quote
I agree. This should be a configuration aspect. But I would suggest to have
it by default set to false. We have to take into consideration that in
testing and staging environments the data sets to work with can be limited
in
catalog and product pages without hitting the database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if caching
is appropriate for the code they are writing.
In theory is it possible to write an entity cache
in the application
server. One real world example of this is the goal to be able to render
ecommerce catalog and product pages without hitting the database.
Over time the entity caching was made more complex to handle more caching
scenarios, but still left to the developer to determine if caching
catalog and product pages without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code they are writing.
In theory is it possible to write an entity cache
without hitting the
database.
Over time the entity caching was made more complex to handle more
caching scenarios, but still left to the developer to determine if
caching
is appropriate for the code they are writing.
In theory is it possible to write an entity cache that can be used
disagree with some of my views, and that is
okay.
Different experiences with OFBiz will lead to different
viewpoints.
The OFBiz entity caching feature is intended to improve
performance
by
keeping GenericValue instances in memory - decreasing the number
of
calls
to the database.
Background
.
Different experiences with OFBiz will lead to different
viewpoints.
The OFBiz entity caching feature is intended to improve
performance
by
keeping GenericValue instances in memory - decreasing the number
of
calls
to the database.
Background
--
Initially, the entity cache was very unreliable
viewpoints.
The OFBiz entity caching feature is intended to improve
performance
by
keeping GenericValue instances in memory - decreasing the
number
of
calls
to the database.
Background
--
Initially, the entity cache was very unreliable due to a
number of
flaws
in its design
Le 19/03/2015 18:46, Adrian Crum a écrit :
The translation to English is not good, but I think I understand what
you are saying.
Oups my apologies !
The entity values in the cache MUST be immutable - because multiple
threads share the values. To do otherwise would require complicated
to be able to render
ecommerce catalog and product pages without hitting the database.
Over time the entity caching was made more complex to handle more caching
scenarios, but still left to the developer to determine if caching is
appropriate for the code they are writing.
In theory is it possible
the entity caching was made more complex to handle more caching
scenarios, but still left to the developer to determine if caching is
appropriate for the code they are writing.
In theory is it possible to write an entity cache that can be used 100% of the
time? IMO the answer is NO. This is almost
to the code that uses them, ie in the
application server. One real world example of this is the goal to be able to render ecommerce catalog and product pages without hitting the database.
Over time the entity caching was made more complex to handle more caching scenarios, but still left to the developer
to render ecommerce catalog and product pages without hitting the database.
Over time the entity caching was made more complex to handle more caching scenarios, but still left to the developer to determine if caching is
appropriate for the code they are writing.
In theory is it possible to write
to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory
with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of calls
to the database.
Background
--
Initially, the entity cache was very unreliable due
will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of calls
to the database.
Background
--
Initially, the entity cache was very unreliable due to a number of flaws
in its
practices I like to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is
okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances
, and some related information.
Some OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing
information.
Some OFBiz experts may disagree with some of my views, and that is
okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of
calls
OFBiz experts may disagree with some of my views, and
that is
okay.
Different experiences with OFBiz will lead to different
viewpoints.
The OFBiz entity caching feature is intended to improve
performance
by
keeping GenericValue instances in memory - decreasing the
number of
calls
to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory
The translation to English is not good, but I think I understand what
you are saying.
The entity values in the cache MUST be immutable - because multiple
threads share the values. To do otherwise would require complicated
synchronization code in GenericValue (which would cause blocking and
best practices I like to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is
okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance
by
keeping GenericValue
, and that is
okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance
by
keeping GenericValue instances in memory - decreasing the number of
calls
to the database.
Background
--
Initially, the entity
Le 18/03/2015 13:16, Adrian Crum a écrit :
If you code Delegator calls to avoid the cache, then there is no way
for a sysadmin to configure the caching behavior - that bit of code
will ALWAYS make a database call.
If you make all Delegator calls use the cache, then there is an
additional
.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of calls
to the database.
Background
--
Initially, the entity cache was very unreliable due to a number of flaws
in its design and in the code that calls
On Mar 18, 2015, at 2:35 PM, Adrian Crum adrian.c...@sandglass-software.com
wrote:
I would be interested in seeing a use case for that.
This is just an example I could think of (there may be other better examples
but I am in a rush and I can't concentrate):
Client code A selects a bunch of
I would like to share some insights into the entity cache feature, some
best practices I like to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity
I would be interested in seeing a use case for that.
I view delegator calls as being no different than SQL statements. Where
in the SQL grammar do you tell the database to get a table row from its
cache or not? That detail is left to the implementation, and in some
cases it can be controlled
to share some insights into the entity cache feature, some
best practices I like to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching
entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of calls
to the database.
Background
--
Initially, the entity cache was very unreliable due to a number of flaws
in its design and in the code that calls
OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of calls
to the database
On Mar 18, 2015, at 1:16 PM, Adrian Crum adrian.c...@sandglass-software.com
wrote:
If you code Delegator calls to avoid the cache, then there is no way for a
sysadmin to configure the caching behavior - that bit of code will ALWAYS
make a database call.
If you make all Delegator calls
On 3/18/2015 1:46 PM, Jacopo Cappellato wrote:
On Mar 18, 2015, at 2:35 PM, Adrian Crum adrian.c...@sandglass-software.com
wrote:
I would be interested in seeing a use case for that.
This is just an example I could think of (there may be other better examples
but I am in a rush and I can't
to follow, and some related information.
Some OFBiz experts may disagree with some of my views, and that is okay.
Different experiences with OFBiz will lead to different viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory
viewpoints.
The OFBiz entity caching feature is intended to improve performance by
keeping GenericValue instances in memory - decreasing the number of calls
to the database.
Background
--
Initially, the entity cache was very unreliable due to a number of flaws
in its design
+1
People often forget that cache memory is hundreds or thousands time
faster that disk access or database references.
Even with the overhead of distributed cache management.
Any extra code required executes at lightspeed rather than rotational
speed or even SSD speed.
It is also easier to
entity caching with filter-by-date
Key: OFBIZ-3090
URL: https://issues.apache.org/jira/browse/OFBIZ-3090
Project: OFBiz
Issue Type: Improvement
Components: ALL COMPONENTS
Resolve widget action entity caching with filter-by-date
Key: OFBIZ-3090
URL: https://issues.apache.org/jira/browse/OFBIZ-3090
Project: OFBiz
Issue Type: Improvement
entity caching with filter-by-date
Key: OFBIZ-3090
URL: https://issues.apache.org/jira/browse/OFBIZ-3090
Project: OFBiz
Issue Type: Improvement
Components: ALL COMPONENTS
49 matches
Mail list logo
