view flys-artifacts/src/main/java/de/intevation/flys/artifacts/access/GaugeAccess.java @ 5779:ebec12def170

Datacage: Add a pool of builders to make it multi threadable. XML DOM is not thread safe. Therefore the old implementation only allowed one thread to use the builder at a time. As the complexity of the configuration has increased over time this has become a bottleneck of the whole application because it took quiet some time to build a result. Furthermore the builder code path is visited very frequent. So many concurrent requests were piled up resulting in long waits for the users. To mitigate this problem a round robin pool of builders is used now. Each of the pooled builders has an independent copy of the XML template and can be run in parallel. The number of builders is determined by the system property 'flys.datacage.pool.size'. It defaults to 4.
author Sascha L. Teichmann <teichmann@intevation.de>
date Sun, 21 Apr 2013 12:48:09 +0200
parents 756aba0d2a7a
children
line wrap: on
line source
package de.intevation.flys.artifacts.access;

import org.apache.log4j.Logger;

import de.intevation.artifacts.CallContext;
import de.intevation.flys.artifacts.FLYSArtifact;
import de.intevation.flys.utils.FLYSUtils;

/** For the moment, light-weight wrapper around FLYSUtils. */
// TODO employ 'Caching' like other Accesses, remove usage of FLYSUtils.
public class GaugeAccess
extends RangeAccess
{
    private static Logger logger = Logger.getLogger(GaugeAccess.class);

    public GaugeAccess(FLYSArtifact artifact, CallContext context) {
        super(artifact, context);
    }


    public String getGaugeName() {
        return FLYSUtils.getGaugename(this.getArtifact());
    }

    // TODO there is also getGauges in FLYSUtils...
}
// vim:set ts=4 sw=4 si et sta sts=4 fenc=utf-8 :

http://dive4elements.wald.intevation.org