You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Emmanuel Bourg (JIRA)" <ji...@apache.org> on 2007/04/10 17:25:32 UTC
[jira] Updated: (CONFIGURATION-180) Cache DatabaseConfiguration
values for higher performance
[ https://issues.apache.org/jira/browse/CONFIGURATION-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Bourg updated CONFIGURATION-180:
-----------------------------------------
Environment: (was: Operating System: All
Platform: All)
Summary: Cache DatabaseConfiguration values for higher performance (was: [configuration] Cache DatabaseConfiguration values for higher performance)
> Cache DatabaseConfiguration values for higher performance
> ---------------------------------------------------------
>
> Key: CONFIGURATION-180
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-180
> Project: Commons Configuration
> Issue Type: Improvement
> Reporter: Stephen Cooper
> Priority: Minor
> Fix For: 1.5
>
> Attachments: dbpreload.txt, Enhancement33553.checkstyle.patch, Enhancement33553.patch
>
>
> The DatabaseConfiguration class queries each property as it gets the request for each property. This is
> nice for ensuring that you're always up to date, but it doesn't give very good performance in enterprise
> applications, where the database may not be on the same subnet.
> What we need is the ability to hit the database once, get all the keys/values and then serve up
> "getString" etc. from that cache.
> I'll be opening a separate enhancement to have a generic Reloading Strategy which could then be
> applied to this caching DatabaseConfiguration approach.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org