In service-client mode, when open TiddlyWiki, it takes about 5 seconds.
CPU: Intel(R) Celeron(R) N5105 @ 2.00GHz
Is it because of slow cpu on server?
In service-client mode, when open TiddlyWiki, it takes about 5 seconds.
CPU: Intel(R) Celeron(R) N5105 @ 2.00GHz
Is it because of slow cpu on server?
I use tiddlywiki with local nodejs. It has 2000 tiddlers, 84 plugins, and is about 30M. But I can also load the page within one second. Can you describe your tiddlywiki environment in detail? Tiddlywiki does not have too many requirements for computer configuration.
About 100 tiddlers, among which 2 tiddlers are list that are generated dynamically e.g.:
<$list filter="[tag[some-tag]sort[title]reverse[]]">
<div>
<$link to={{!!title}}>
<$view field="title" />
</$link>
<% if [<currentTiddler>tag[done]] %>
✓
<% endif %>
</div>
</$list>
Many tiddlers contain imported images.
It totally takes about 180MB on disk.
The speed of lan is 1000Mb/S.
Maybe it’s a problem with the image. I remember there is a parameter for lazy loading of images.
Alright, with tiddlywiki --listen root-tiddler=$:/core/save/lazy-images
, it becomes very fast.
I think i should be by default.
doc at https://tiddlywiki.com/static/LazyLoading.html
Thanks
I’ve read it, the doc is not very clear.
Anyway if it is the best way, it also should be by default.
I have not decided which note taking software to use yet.
Thanks
It is the best way to handle large images or large numbers of images. But it also breaks the one-file-per-wiki pattern of TW. I would absolutely not want it on by default.
For example, I have a wiki used to manage my chess club at work. The three club administrators make changes in it and email the results back and forth. (Someday, I’ll find some online Node hosting for it.) Among the 750+ tiddlers are around 125 images, most of which are photos of members. But we use relatively small photos, and the entire wiki is around 6.7 MB, small enough to easily email. If the images were external, we would have to zip up a folder of it, email that, and unzip upon receipt. While I’m a programmer, and another administrator is a QA person with technical skills, our third administrator is a lawyer. Asking him to do that would be problematic.
It’s great that external images are available for image-heavy wikis. But I definitely would not want them to be the default.