On Thu, Feb 23, 2012 at 3:55 PM, Bertrand Guay-Paquet <ber...@step.polymtl.ca> wrote: > First of all, you stated that your problem what that the serialized size was > too big, so please don't be so rude. > > Now, are you sure that the slow part of serialization is not the IO for > storing that 10MB? If it is, zipping the page could definitely improve > performance, even if it takes a some CPU time to do the operation.
Storing of the bytes in the disk is asynchronous by default. > > Bertrand > > > On 23/02/2012 12:04 AM, Martin Makundi wrote: >> The problem is that the SERIALIZATION takes time. So it does not help to >> ZIP AFTER serialization... >> I have debugged it and it's just thousands and thousands of components. >> Even printing the component paths alone take almost 10mb or more because >> there is repetition ;) >> ** >> Martin >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
