Attachment performance with "Folders"

200 views
Skip to first unread message

Marc Fargas

unread,
Mar 29, 2019, 4:32:47 AM3/29/19
to TiddlyWiki
Hi,

I'm very new at Tiddly (like.. yesterday).

Dropping PDF's on a tiddler seems very usefull, but on #Performance it says I should avoid having a very large Tiddly... aka, I should avoid filling tidlly with lots of PDF.

Question is... Is this true also when using the TiddlyWikiFolder structure? Or does it only matter when using the single file format?

Also, are the blobs loaded into memory no matter what (either server or client) or only when the tiddle is open? (on WikiFolder format)

Thanks,
marc

TonyM

unread,
Apr 4, 2019, 11:55:19 PM4/4/19
to TiddlyWiki
Marc,

Since no one has answered I will point you to the idea of external files using "canonical" or skinny tiddlers, these are key words that should get you somewhere on this.

Depending on your application I would first try filling up your wiki with your PDF's as a trial and see if they damage the performance.

Regards
Tony

Jed Carty

unread,
Apr 5, 2019, 3:30:45 AM4/5/19
to TiddlyWiki
If you are using a single file wiki than everything has to be loaded before the wiki can function, this includes all embedded pdfs and other media. Tiddlywiki can reference and display external media. Either using _canonical_uri fields as Tony suggested or by directly linking to the me media, the two are mostly equavient and which one you use is just a matter of taste. See here https://tiddlywiki.com/#ExternalImages and here https://tiddlywiki.com/#Images%20in%20WikiText for some references.

Using either method you can get around much of the problem by letting the browser handle the memory management. If you do that than only the media in open tiddlers will necessarily be loaded into memory. I think that the specifics are up to the browser caching policy.

If you have 10000 images than using external images is a better idea.

Depending on your usage of TiddlyWiki you may be better off using the node version.

Bob may help with this, is it a plugin for tiddlywiki that I packaged into a single executable file that takes care of saving and some management of multiple wikis https://github.com/OokTech/TW5-BobEXE/releases

Marc Fargas

unread,
Apr 16, 2019, 4:25:39 AM4/16/19
to TiddlyWiki
Thanks for the tips TonyM & Jed.

I am currently testing with Bob. Let's see how far I get before it explodes!

Thanks,
marc

Mark S.

unread,
Apr 16, 2019, 4:40:42 PM4/16/19
to TiddlyWiki
You don't mention this possibility, but could you use

root-tiddler=$:/core/save/lazy-all

in the ws-server section of the config file of Bob, to activate lazy serving?

Thanks !
-- Mark

Jed Carty

unread,
Apr 17, 2019, 3:58:25 PM4/17/19
to TiddlyWiki
Mark,

I don't think that would work, but I haven't every tried. I haven't put anything in the server to handle lazy loading.

Mark S.

unread,
Apr 17, 2019, 4:53:22 PM4/17/19
to TiddlyWiki
Somehow I assumed it was using Jeremy's code as a basis, and so would use the same settings for --listen.

If it could use lazy-loading, then you effectively no longer have to worry about externalizing images (except for image-intensive apps like photo-galleries).

Thanks!
-- Mark
Reply all
Reply to author
Forward
0 new messages