Re: GAE serialization issues
Hi dear thanks for the reply i 'm in the first steps of application deployment on appengine with no problems so far with my manual testing and with jmeter if u have any tips or hints , that will be greatly appreciated Thanks Joe On Thu, Apr 29, 2010 at 5:30 PM, jbrookover wrote: > > I can only say that I've been using Wicket on GAE for awhile and it seems > to > work pretty well, with some extra effort. For now, I'm just using > HttpSessionStore. I asked in the GAE forums about the performance there > and > they said session storage made heavy use of the MemCache to keep > performance > strong. It is possible that Wicket can store very LARGE objects in the > SessionStore, but that may be an indication of poor page detaching. After > making that improvement, my session data rarely exceeds 100K. > > I may try out a pure MemCache version based on the link you provided, see > if > I can get it lower and less dependent on the session. > > The only other serialization issues I've noticed deal with changing model > objects across requests - I instead am forced to replace components on > occasion, instead of replacing model objects. That's a hack right now and > I'll look into it later. > > Don't know anything about JBoss. > > Jake > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/GAE-serialization-issues-tp2068427p2075571.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: GAE serialization issues
I can only say that I've been using Wicket on GAE for awhile and it seems to work pretty well, with some extra effort. For now, I'm just using HttpSessionStore. I asked in the GAE forums about the performance there and they said session storage made heavy use of the MemCache to keep performance strong. It is possible that Wicket can store very LARGE objects in the SessionStore, but that may be an indication of poor page detaching. After making that improvement, my session data rarely exceeds 100K. I may try out a pure MemCache version based on the link you provided, see if I can get it lower and less dependent on the session. The only other serialization issues I've noticed deal with changing model objects across requests - I instead am forced to replace components on occasion, instead of replacing model objects. That's a hack right now and I'll look into it later. Don't know anything about JBoss. Jake -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/GAE-serialization-issues-tp2068427p2075571.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: GAE serialization issues
Hi Any ideas? please i need these info asap ,i appreciate your help thanks Joe On Wed, Apr 28, 2010 at 1:45 AM, Joe Fawzy wrote: > Hi everybody > i am developing an application on the GAE/J platform using wicket > as i read through this list ,it seems that it is not a recommended > combination due to some issues , specially the serialization issue > BUT i have to deploy on appengine, so what is there any recommendations? > > OK, the real question is: >does anyone used the custom PageStore implementation described in: > http://letsgetdugg.com/2010/02/07/clustering-wicket-for-fun-and-profit/ > or in: > http://www.mail-archive.com/users@wicket.apache.org/msg46421.html > > in production and found that of real help? > if so which one is better? > what are the side effects of using each? > can i have an implementation that fallback to normal sessionStore? > > Another question > as its related to seialization, can using JBoss serialization lib make > difference in GAE case? as it is much faster > if so where are the hooks , or the interfaces to replace the default > serialization > BTW. i know it cannot be used in the core wicket due to its LGPL lic. > > Thanks > Joe > > >
GAE serialization issues
Hi everybody i am developing an application on the GAE/J platform using wicket as i read through this list ,it seems that it is not a recommended combination due to some issues , specially the serialization issue BUT i have to deploy on appengine, so what is there any recommendations? OK, the real question is: does anyone used the custom PageStore implementation described in: http://letsgetdugg.com/2010/02/07/clustering-wicket-for-fun-and-profit/ or in: http://www.mail-archive.com/users@wicket.apache.org/msg46421.html in production and found that of real help? if so which one is better? what are the side effects of using each? can i have an implementation that fallback to normal sessionStore? Another question as its related to seialization, can using JBoss serialization lib make difference in GAE case? as it is much faster if so where are the hooks , or the interfaces to replace the default serialization BTW. i know it cannot be used in the core wicket due to its LGPL lic. Thanks Joe
