Re: zOGI & Consonance

> Adam Tauno Williams wrote:
> >The current *BIG* problem is that it really needs to
> > use an on-disk cache and the filtering of tasks for the list needs to be
> > more efficient,  when aimed at a production server it gets really bogged
> > down.  Anyone familiar with db4o? :)
> db4o just for caching sounds a bit overkill, what about the builtin 
> support to serialize objects (or hashtables) in Mono/.NET?
> See: http://www.codeproject.com/dotnet/phonebook.asp

Which doesn't gain anything if I have to un-serialize/instantiate all
the objects in order to do a lookup/search.  I'm back to walking through
a huge Hashtable, which is what I do now;  the lowest end machine I
intend to 'support' is a 1.xGHz Celeron w/2Gb of RAM, and that takes way
too long.  Having a searchable cache is key,  and it is my understanding
that db4o can be searched and recent versions even support indexing on
properties.  A searchable on-disk cache also opens up the possibility of
an offline mode.

But saving the in-memory cache to disk at application exit so I have
something to start with next time might help in the interim.

Also I'll probably remove the Archived tab from the task list widget
since that will reduce the number of objects significantly.  Currently
the task list widget has a Gtk.ListStore of all the task objects known
to the application;  each TreeView in the task lists
[to-do/delegated/assigned/...] accesses the one Gtk.ListStore through a
Gtk.TreeModelFilter.  This works well and keeps things current but means
every time a task gets touched it executes a filter function on every
task object x 4.  That is about (2200 x 4) if I point it any my
production server. :)

signature.asc
Description: This is a digitally signed message part