Plans for Loggerhead

[Martin Albisetti]

On Wed, Jan 7, 2009 at 12:34 AM, Robert Collins
<robertc at robertcollins.net> wrote:
>> Used to render the actual html via javascript.
>
> Where does this rendering take place? On the loggerhead server, or in
> the browser?

Browser. A lá gmail.


> I'd be extremely wary of overlapping with bzrlib here; fundamentally the
> basics of loggerhead should be very thinly layered on bzrlib, if
> something is too slow to show to a user in web time using bzrlib
> directly, anything added on top is just complexity that will interfere
> as bzrlib gets fixed to be fast enough. This has happened a few times
> already - and when I look at loggerhead performance on brisbane core its
> mainly using convoluted approaches on top of bzrlib api's that are
> slower than they should be on production branches.

I fully agree. The problem is that I don't have the knowledge to dive
into bzrlib and do the fundamental changes needed, and many of the
performance problems have been well known for quite a while (ie,
revnos), and nobody has managed to find time to fix it. It's the
nature of all projects, so it's perfectly understandable. I'm just
trying to take an approach I can handle myself, and fundamentally
fixes the problems we have today.
There's also something else, which has nothing to do with bzr at all,
which is the need to refactor the internals of Loggerhead to make it
less painful to keep on adding features. My thoughts where, if I'm
going to be re-writing, I'd rather take on the opportunity and think
about it more broadly.


-- 
Martin