esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Kohler <markus.koh...@gmail.com>
Subject Re: Memory allocation and lazy vals
Date Sat, 28 Nov 2009 16:23:33 GMT
Sure,
I hope I will have some time to do this tonight.
Regards,
Markus
"The best way to predict the future is to invent it" -- Alan Kay


On Sat, Nov 28, 2009 at 4:46 PM, Richard Hirsch <hirsch.dick@gmail.com>wrote:

> @Markus:  Can you please kick the tires on the "new" / "old" ESME?
> Let's see what a repaired ESME can do.
>
> :->
>
> D.
>
> On Sat, Nov 28, 2009 at 4:42 PM, Vassil Dichev <vdichev@apache.org> wrote:
> > If it sounds stupid, then it probably is. Lazy vals work fine. One
> > thing to have in mind is that a lazy val is null, it will be
> > reevaluated again (the first thing that tripped me).
> >
> > The problem is that I relied on findMessages working correctly. It
> > didn't. Unfortunately the changes from access pools made it to always
> > hit the DB and not try the cache. I've fixed it now. (tests, tests,
> > tests)
> >
> > As a result, ESME is now as fast as we remember it from the beginning.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message