Recent list has come up many times as an issue in this thread. How can we
limit it to the last 10/20/etc. tiddlers? I'm tempted to drop it altogether
in my tws.
On Sat, Sep 21, 2019, 9:00 AM @TiddlyTweeter,
wrote:
> TonyM wrote:
>>
>> Actualy I think there may be some fundamental assumptions
TonyM wrote:
>
> Actualy I think there may be some fundamental assumptions made in the
> typically sized wikis that a wrong at scale. For example the recent
> tiddlers list can get very large. When saving the noscript section can add
> a 50% to file size.
>
> Somehow Jeremy and others avoid
Actualy I think there may be some fundamental assumptions made in the typically
sized wikis that a wrong at scale. For example the recent tiddlers list can get
very large. When saving the noscript section can add a 50% to file size.
Somehow Jeremy and others avoid this at scale as did my
TonyM wrote ...
It is a solution and a work around but the root cause is not yet known
That is a *very *interesting comment.
It would be very useful to pin it down.
Is it about reducing dynamic recursion in wikis with umpteen Tiddlers?
I have been inhibited from making large scale wikis of
Footnote.
I just tested TonyM's version on Android 8. Chrome browser. Online version.
Its works, on first look, just as well as via Desktop.
That's really good news for apps like that.
Take your dictionary with you!
Best wishes
TT
> TonyM wrote:
>>
>> http://tiddlywiki.psat.com.au/ESPDIC
Hi Mat,
Firefox or Chrome?
Reading TT. I tried the downloaded file in Chromium, it absolutely didn't
run, but it walked. (I mostly find Chromium faster than Firefox, but I like
to work in Firefox better.
Linux Mint Mate 19.2 8gb
Tony's work is by far the fastest.
lørdag den 21. september
>
> http://tiddlywiki.psat.com.au/ESPDIC
>>
>
> This version worked fine for me on a short test. Mark's original didn't.
>
Same experience for me - downloaded file poor performance, online file
works quite well.
Win10, 4GB
<:-)
--
You received this message because you are subscribed to the
TonyM wrote:
>
> http://tiddlywiki.psat.com.au/ESPDIC
>
Quick note.
This version worked fine for me on a short test. Mark's original didn't.
Win 10, 64. 4GB memory. Dual core. Tested online version, not downloaded
file.
Tested in Chrome & Chromium-Edge.
Best wishes
TT
--
You received this
Hi Mark,
When upgrading my very old wiki I did export my tiddlers and reimport them
after having changed the "old ways" of doing things. It did help just
enough for me to divide my tiddlers and export them for use with 3 of my
other wikies. (it made more sense in my case).
@Tony just followed
Hi Mark,
I referred to the old thread mostly because Dave Gifford said he could not
feel a slow down until 100mb, Jeremy admitted he had to give up at 60 mb
then.
That indicate to me, that hardware has to do with it.
Also that the improvements in hardware in the years to come will better
I didn't try out anything but here are a few thoughts:
- Do browsers accept any size of a webpage for all it's tools and
operations? I.e might some thing kick in or turn off in browsers at a
certain stage? Might TW in particular trigger or or off something that
browsers rely on? If
Post Script,
I forgot to mention on my demoI have created a info plugin tiddler with ESP
words in it, and operating on its shadow tiddlers. this may have the result
of keeping them out of other searches and improving performance.
Regards
Tony
--
You received this message because you are
Mark,
I have had a chance to work on this today, but may not tomorrow. Because of
my long term investment in the tiddlywiki platform, both personally and
professionally I want to ensure I identify the limitations and ways to
overcome them.
When building a custom search I saw the performance
Hi Birthe,
Strangely enough, I didn't remember a thread from 2013 ;-)
Back then, Jeremy was saying an upper limit was around 100 mb. Now I think
he's suggesting 800mb (or was it more?) is feasible.
Thanks!
On Friday, September 20, 2019 at 5:47:03 PM UTC-7, Birthe C wrote:
>
> Mark,
>
> Did
Hi Tony,
That's very interesting. Why should deleting and then re-importing make a
difference? Unless the way I created them bypassed the new optimization
technology.
Maybe @Birthe could try exporting and re-importing her data as well, to see
if her TW performance improves.
I might mention
Ok Mark,
I have something *resembling a solution*. These are the steps I took and
from this we may draw some conclusions.
*Is there a Tiddlywiki ribbon I get?*
It is a solution and a work around but the root cause is not yet known.
- ESPDIC wiki - exported all tiddlers tagged Vorto to
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
Mark,
Did you mention optimizations?
Do you recall an earlier thread concerning Dave Giffords Photoalbum...and
the wonderfully humorous answer from Jeremy
https://groups.google.com/forum/#!searchin/tiddlywiki/TW5$20image$20gallery/tiddlywiki/PpJsdJr99n8/nY-9eAXGB6YJ
Great, greater, greatest
Mark,
I got to try your wiki on my friends pc with 12 gb ram. That did not give
any big difference, it would not like to edit it. (Just thought it would be
fun to know)
Birthe
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe
I am using the latest 5.1.21 - just upgraded yesterday.
I does not take as long to read as yours in my browser, it is slow to
navigate, but as you are experiencing. - terrible to impossible to edit.
I can add, that last time I tried TW translators edition I had the same
feeling, I really had to
Thanks Birthe.
What TW version are you using? 5.1.20 was/is supposed to have optimizations
that allowed larger TW's.
Thanks!
On Friday, September 20, 2019 at 4:56:43 PM UTC-7, Birthe C wrote:
>
> Mark,
>
> My pc also has 8 gb ram. One of my wikies are about the same size and has
> nearly the
Mark,
My pc also has 8 gb ram. One of my wikies are about the same size and has
nearly the same amount of tiddlers. I have very little shown in the
sidebar. The tiddlers a very short text, very little filtering . Very
simple wiki indeed. But it is just as slow and difficult to work with as
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
If you want to try a more optimized search then open up the Dictionary
Manager tiddler
and change this line:
<$set name="listfilter"
value="""[tag[Vorto]regexp:en[\bcat\b]sort[title]limit[10]]""">
to
<$set name="listfilter"
value="""[tag[Vorto]match:title[kato]sort[title]limit[10]]""">
Or
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
Mark,
I am getting some performance issues as well. I did hear my computer waking
up to get disk or cpu to operate.
The example you have provides still relies on the sidebar and standard
search. Have you tried to implement some of my changes in the previous post
in your own copy?
By opening
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
I just noticed before you replied - ooops
Looking now
On Saturday, September 21, 2019 at 8:55:26 AM UTC+10, Mark S. wrote:
>
> Hi Tony,
>
> Perhaps you didn't see the prior post. You can download what I have so far
> at
>
> https://github.com/Marxsal/EODIC
>
> It could very well have
Hi Tony,
Perhaps you didn't see the prior post. You can download what I have so far
at
https://github.com/Marxsal/EODIC
It could very well have something to do with machine capabilities and
memory. My current box only has 8 Gig.
Thanks,
Mark
On Friday, September 20, 2019 at 3:48:47 PM
Mark,
Perhaps if you can't share your wiki publicly perhaps you can privately to a
few of us. With privacy assured.
There would be value in looking into browser memory like I suggest in a
previous reply.
I find timimi is the quickest but I do use Windows 10 64bit with 16gb of ram.
And
Thanks for the reply!
It can be retrieved from:
https://github.com/Marxsal/EODIC
How do we get the output out of the console? It loses all the table
formatting when I try to copy it.
Thanks!
On Friday, September 20, 2019 at 8:20:07 AM UTC-7, Jeremy Ruston wrote:
>
> Hi Mark,
>
>
Hi Mark,
Interesting! I’d echo the request to share the wiki if you’re able to.
Perhaps you could use the performance instrumentation tools to see if any
filters are bottlenecks:
https://tiddlywiki.com/#Performance%20Instrumentation
In particular, after turning on performance instrumentation
32 matches
Mail list logo
