[@All] Mojarra Important Perfomance Problems

[cagatay.civici]

Thomas, are you the author of JSF Stateless project? The author of the arcticle is Rudi Simic;

http://industrieit.com/blog/2011/11/sta ... -overhead/

[tandraschko]

No, but the stateless Extensions is only for Mojarra. I created an project, out of this original, with support for mojarra and myfaces

[cagatay.civici]

Great! Thanks.

[KingdomHeart]

Hi Thomas, when you said

I think it will not be accepted. The code seems to be inefficient - i didn't check this with a profiler. Also the improvement is much lesser then with mojarra.

Do you mean the code from the original developer is inefficient?

[tandraschko]

Hi,

here is the mailing list entry:

http://comments.gmane.org/gmane.comp.ja ... evel/54352

[membersound]

Out of curiosity I've tested the sample page at;

http://java.net/jira/browse/JAVASERVERFACES-2334

Mojarra ajax results averaged 1000ms and MyFaces ajax results averaged 50ms so difference is huge. Difference ratio also applies to non-ajax requests.

So the topic should be Mojarra Performance Problems, there is an obvious bottleneck in mojarra code.

Can someone instruct me in how to measure my app?
I too have those performance problems, and tried for days to "optimize" my app without success. now, switched just to myfaces, it runs VERY much better.
How do you guys measure this?

[smithh032772]

Very interesting topic. I wonder if I should consider MyFaces over Mojarra.

@membersound, I saw the following mentioned at the URL that you just referenced in your post/response. You might search google for DynaTrace.

adrian_e added a comment - 09/Mar/12 04:04 PM

I would like to add one additional data point. I also tested the example code with DynaTrace (Free AJAX Edition) - it's a free product that is basically FireBug on steroids. You can drill down to the nth degree to see where the bottlenecks are.

[nicolasr]

Hello,

I noticed that my pages were slow to load too (ajax as well). I run jprofiler and realized most of the CPU was spent in PrimeResourceHandler (which is just a wrapper).
I also noticed that this was mainly due to the few composite components my page is using.

Do you use composite component?

In my case, the patch below enabled me to really boost my performances (code is self explanatory).
make sure you declare it in your faces-config.xml as this:

Code: Select all

<application>
        <resource-handler>yourpackage....PrimeResourceHandlerWithCache</resource-handler>

Code: Select all

import java.util.HashMap;
import java.util.Map;

import javax.faces.application.Resource;
import javax.faces.application.ResourceHandler;

import org.primefaces.application.PrimeResourceHandler;

/**
 * This class to circumvent performance limitations observed when using composite component.
 * Indeed, createResource is invoked over and over and consumes a lot of cpu.
 */
public class PrimeResourceHandlerWithCache extends PrimeResourceHandler {

    private Map<String, Resource> resCache = new HashMap<String, Resource>();

    public PrimeResourceHandlerWithCache(ResourceHandler wrapped) {
        super(wrapped);
    }

    @Override
    public Resource createResource(String resourceName, String libraryName) {
        String key = resourceName + "__" + libraryName;
        Resource resource = resCache.get(key);

        if (resource == null) {
            resource = super.createResource(resourceName, libraryName);
            resCache.put(key, resource);
        }
        return resource;
    }
}

[cagatay.civici]

Please file an issue and we will look about create resource.

[Oleg]

Regarding to Stateless JSF and performance. Thomas made a comprehensive comparison between Stateful and Stateless JSF, Mojarra and MyFaces, with less and many components on a page. Perhaps he can share this statistic here.