7 Replies Latest reply on May 22, 2008 8:56 PM by Richard Ogin

    Performance issue related to Conversation scope

    Richard Ogin Newbie

      I have a CONVERSATION scoped bean that holds a Map of many items (over 1k). The bean works quickly when the Map is not populated OR the scope is set to SESSION. The problem arises when the Map is populated AND the scope is set to CONVERSATION. The problem is that a call is executed but my CPU usage goes through the roof and the page fails to update for over 10 seconds. So I call a method, debug info shows it immediately completes, but Seam appears to hate the Map of many items at that scope. I assume it is reading the bean from a scope cache and writing it back to the cache or something which costs it so much CPU time. Has anyone else run into something similar? I googled a bit and searched this forum, but I failed to find anything that really matched my situation.