Re: Opera Memory Fix

["Kevin Kubasik" <kevin kubasik net>]

Ok, on the FSQ thing, its far too dynamic to do something on-disk, we
would thrash it.

There is however a leak at FileSystemQueryable.cs 345, its not the
most horrid offender, but it can be one.

The real issue is the reflection/serialization stuff, some of this
might be mono issues, some might be on us, but there are a ton of
strings hanging around in the XML serialization class libraries. There
are over 8,000 System.MonoType instances that pretty much hang around
(apperently they are not collectable, and abundantly used in
reflection) . I'll keep the list posted if I discover anything we can
do to reduce it.

On Nov 16, 2007 8:07 AM, Kevin Kubasik <kevin kubasik net> wrote:
> On Nov 16, 2007 7:37 AM, Debajyoti Bera <dbera web gmail com> wrote:
> > > > Also, do you know if Dictionary<> offers a performance/memory  benefit
> > > > over Hashtable? I found this which leads me to think it should be at
> >
> > It shouldn't (when storing objects). If you are referring to a FIXME in
> > InteralUriManager about using Dictionary instead of Hashtable, it is because
> > of cleaner code, not performance.
> I kinda figured that was  the intent of the comment, just didn't know
> if anyone new of an advantage. I'm doing some debugging runs to get
> real FSQ numbers now.
> >
> > --
> > -----------------------------------------------------
> > Debajyoti Bera @ http://dtecht.blogspot.com
> > beagle / KDE fan
> > Mandriva / Inspiron-1100 user
> > _______________________________________________
> > Dashboard-hackers mailing list
> > Dashboard-hackers gnome org
> > http://mail.gnome.org/mailman/listinfo/dashboard-hackers
> >
>
>
>
> --
>
> Cheers,
> Kevin Kubasik
> http://kubasik.net/blog
>



-- 
Cheers,
Kevin Kubasik
http://kubasik.net/blog