Mark,
I am continuing to research this here is a little of my work product
Longer time outs and waiting can be better than multiple continue prompts.
I would definitely add a splash screen to this wiki.
I can see what you are experiencing but not as severe. By using a taylored
search in the only tiddler displayed and the side bar closed I get further
improvements. I have not yet set a submit search that only searches once
you hit submit.
Try this and see if there is a marked improvement or not
Vorto/Title/prefix search
<$edit-text tiddler="$:/temp/search/title" tag=input/>
<$list filter="[{$:/temp/search/title}minlength[3]]">
Number found: <$count filter="[tag[Vorto]prefix{$:/temp/search/title}]"/>
<br>
<details>
<$list filter="[tag[Vorto]prefix{$:/temp/search/title}]">
</$list>
</details>
</$list>
My hunch is tiddlywiki is rendering something with every keystroke and
action that is impacted by the scale of the wiki. Its obvious with a search
that changes every key stroke but not before the 3 character limit is
reached in my example.
I just tried it
through a local TiddlyServer and its a little slower but similar.
through TiddlyDesktop and its faster but still not easy to use.
*Hey could this be it?*
*I closed all tiddlers and sidebar and did a firefox developer inspect, to
see what is actually presented in this view and possibly damaging
performance*
- I found a noscript area for when Java script is not available full of
static tiddler links (Presumably all tiddlers). I deleted this from the HTML
- Then on inspect again I find the div id=storeArea appears to list
every tiddler, this may be normal operation however the inspector lists a
few pages then says
- some nodes were hidden. And a button to Show all 72157 nodes, this
is a large number and seems to be twice your 36,000 words.
- This looks suspicious.
We now need some serious skills to advise.
Regards
Tony
On Saturday, September 21, 2019 at 9:50:04 AM UTC+10, Mark S. wrote:
>
> Yes, I already have this set to a two minute timeout:
>
>
> https://support.mozilla.org/en-US/kb/warning-unresponsive-script#w_letting-the-script-run-longer
>
> but of course, that just gets the messages out of the way. You still have
> to wait ...
>
> Thanks!
>
> On Friday, September 20, 2019 at 4:36:55 PM UTC-7, TonyM wrote:
>>
>> Birthe,
>>
>> There are timeouts I commonly increased in browsers to stop this kind of
>> error message, at least in earlier versions. I expect they remain in my
>> browser settings.
>>
>> Tiddlywiki does do more than most things in the browser.
>>
>> Regards
>> Tony
>>
>> On Saturday, September 21, 2019 at 9:15:49 AM UTC+10, Birthe C wrote:
>>>
>>> Sure enough, Firefox constantly complaining, a webside is slowing, do
>>> you want to wait?
>>>
>>>
>>> Birthe
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/886c7409-dd2e-4d73-9cd5-25677d0dfb36%40googlegroups.com.
