why are these tiddlers created? 1-{-1642131862}

[Adam Winn]

hey everyone,

                     I just upgraded to the newest version, when I imported I noticed a ton of tiddlers in the format above. they all have titles for my tiddlers in them as well. what are these?

thanks

[Danielo Rodríguez]

Hello,

I made the same question when I started and people encouraged me to investigate it. I just leaved it apart:-P and I discovered it just some weeks ago.

They are state Tiddlers. Any widget that needs a temporary unique place to store information creates that kind of Tiddlers. You can freeley remove them

In my opinion it would be better if they are not treated as regular Tiddlers.

[Adam Winn]

Ah, thank you.

I remember hearing about those. nice to know what they are now.

will they affect performance if there are a ton of them? 

my Wiki gets laggy after using it for a little while. I want to figure out why. I have a google calendar embeded and a calculator widget using iframes. I am also using only tabs for my navigation. 

I also created a directory tiddler with tabs that contain every other tiddler. I think that this might be the most probably cause, but I am not the best with dev tools or firebug so I  am at a loss for how to really track it down. suggestions?

[Danielo Rodríguez]

The best way would be to get an empty tiddlywiky and import to it your customizations. This way you will have two advantages : you can figure if your customizations are the root of your performance problem and you will be able to share it with others to be analyzed.

Regards.

[PMario]

will they affect performance if there are a ton of them?

I don't know, what is "a ton of them" for you :) ... 

I did some tests with about 20'000 [1] tiddlers each one about 800bytes of content, and the sidebar gets slow, but still useable.
Editing tiddlers gets slow, with so many tiddlers, if your "Recent" tab is activated. If "Open" is used it works.

So I guess it's your included 3rd party stuff, that makes TW slow.

I did a second [2] test with 100'000 tiddlers, wich imo breaks the browsers :)

I did the 20'000 tiddler [1] test again, since TW has changed some input handling. ... IMO up to 5'000 text tiddlers you should be fine. ... Also depending on your computer hardware.

have fun!
mario

[1] 20'000 tiddlers
https://groups.google.com/forum/#!msg/tiddlywiki/E9DMg4ZTccw/P1qjS_-HOjAJ

[2] 100'000 tiddlers
https://groups.google.com/d/msg/tiddlywiki/sH4EZukozdM/PM4P3Iy_iWoJ

[Matabele]

Hi

I don't know about performance, but the state tiddlers clog up the system tab -- I have taken to saving <<tabs>> macro and <$reveal> widget states to fields rather than to the text field of a tiddler.

This involves specifying a target field in the <<tabs>> macro. This appears to work best when a field of the tiddler containing the <<tabs>> macro is used -- although a field may be targeted in a special '$:/tabs/states' tiddler if preferred (ensure there are no duplicates.) It is preferable to specify the full text-reference, particularly when tiddlers are transcluded -- this ensures that the same field always stores the same state.

The syntax:

<<tabs "[[filter expession]]" "default tab" "Target-tiddler!!target-field">>

regards

[Terry Jones]

don't know if the contents of $:/HistoryList will specifically erode performance, but it takes space, increases load and save time, etc.