FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.



Sep 13, 2011, 6:29 AM
122 Posts

Performance of Java Class vs Domino collections

  • Category: Managed Beans in NSF
  • Platform: All
  • Release: 8.5.2
  • Role: Developer
  • Tags: Java,Managed Beans,performance
  • Replies: 1
I've been using managed beans more and more recently for, amongst other things, ease of use. What are the performance implications of using a managed bean to create Java objects from collections, to manage CRUD processes? Are they much slower?
 
I assume that although the normal XPage lifecycle recycles the relevant NotesDocuments and does not write to disk / store in memory (because of serialization). But I guess that the values written to the XPage or bound via Expression Language do actually get written to disk / stored in memory, along with the UNID / note ID to allow the NotesDocument to be accessed again. So there is no memory impact of using a Java bean rather than Domino documents.
Oct 3, 2011, 4:36 PM
18 Posts
Re: Performance of Java Class vs Domino collections
Paul,
 
were just getting into this here, have you come to any conclusions ?

FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.