TimeToLiveSeconds and timeToIdleSeconds ehcache configuration

configurationehcache

My app sometimes goes unused for 24 hours or more but when it does get a request, it is very slow because the data has to be fetched from database. Here is the current ehcache configuration:

 timeToIdleSeconds="120"
 timeToLiveSeconds="120"

I am considering using the following configuration:

 timeToIdleSeconds="172800"
 timeToLiveSeconds="0"

i.e. it never expires according to timeToLiveSeconds and the cache waits 48 hours (48*60*60=172 800) after last access before expiring.

Does that make sense at all?

Thanks in advance,

Julien.

Best Answer

That makes sense, the default settings of 120/120 are definitely not working for you. Also make sure you set eternal="false", since having it true overrides the timeToIdle and timeToLive settings.

Related Solutions

Spring – Difference between using bean id and name in Spring configuration file

From the Spring reference, 3.2.3.1 Naming Beans:

Every bean has one or more ids (also called identifiers, or names; these terms refer to the same thing). These ids must be unique within the container the bean is hosted in. A bean will almost always have only one id, but if a bean has more than one id, the extra ones can essentially be considered aliases.

When using XML-based configuration metadata, you use the 'id' or 'name' attributes to specify the bean identifier(s). The 'id' attribute allows you to specify exactly one id, and as it is a real XML element ID attribute, the XML parser is able to do some extra validation when other elements reference the id; as such, it is the preferred way to specify a bean id. However, the XML specification does limit the characters which are legal in XML IDs. This is usually not a constraint, but if you have a need to use one of these special XML characters, or want to introduce other aliases to the bean, you may also or instead specify one or more bean ids, separated by a comma (,), semicolon (;), or whitespace in the 'name' attribute.

So basically the id attribute conforms to the XML id attribute standards whereas name is a little more flexible. Generally speaking, I use name pretty much exclusively. It just seems more "Spring-y".

Ruby-on-rails – How to define custom configuration variables in rails

In Rails 3, Application specific custom configuration data can be placed in the application configuration object. The configuration can be assigned in the initialization files or the environment files -- say for a given application MyApp:

MyApp::Application.config.custom_config_variable = :my_config_setting

Rails.configuration.custom_config_variable = :my_config_setting

To read the setting, simply call the configuration variable without setting it:

Rails.configuration.custom_config_variable
=> :my_config_setting

UPDATE Rails 4

In Rails 4 there a new way for this => http://guides.rubyonrails.org/configuring.html#custom-configuration

enter image description here

Best Answer

Related Solutions

Spring – Difference between using bean id and name in Spring configuration file

Ruby-on-rails – How to define custom configuration variables in rails

Related Topic