IIRC v3, and late versions of v2 i think, had the super-speedy-indexed
tagging.  I'm kinda surprised that 3 was so much slower than 2.x...
usually that kind of slowdown means something is scanning every
tiddler (often it happens each time the view refreshes).  I guessing
you would have mentioned any additional plugins that might be doing a
full tiddler scan.

Did you try Prism?  How'd that go?

:Daniel

On Fri, Jul 3, 2009 at 10:27 AM, Nils Davis<[email protected]> wrote:
>
> I just tried upgrading to TW 2.5.x and mGTD 3.<whatever> and saw an
> incredible slowdown from my old TW 2.2 + mGTD 2.1. Every change in a
> tiddler (action, project, whatever) resulted in long periods of 100%
> cpu usage. Eventually those periods would end. For now I'm sticking
> with the old version. If this is simply the issue with the looping
> through the side bar, I can definitely workaround that as directed
> somewhere, but is it expected that this operation got so much more
> expensive between 2.2/2.1 and 2.5/3.<whatever>?
>
> Nils
>
> On May 24, 3:15 am, Daniel Baird <[email protected]> wrote:
>> On Wed, May 20, 2009 at 6:20 AM, Jonathan El-Bizri <[email protected]> wrote:
>>
>> > Hello all,
>> > [...]
>> > I’m sure I’m not alone in needing a faster implementation of mGTD.
>> > Suggestions? This hasn't been addressed to any satisfaction anywhere I
>> > look.
>>
>> Are you using v3 of mGTD?  Or still on v1 or v2?
>>
>> ;Daniel
>>
>> --
>> Daniel Baird
>> I've tried going to the XHTML <bar /> a few times, but it's always closed.
>
> >
>



-- 
Daniel Baird
I've tried going to the XHTML <bar /> a few times, but it's always closed.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GTD 
TiddlyWiki" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/GTD-TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to