Performance Issues

(Redirected from How big can my file get before it gets too slow/doesn't work?)

Jump to: navigation, search

This page's contents need to be reviewed and/or refactored to comply with TiddlyWiki.org's quality standards.

I recommend disabling animations even on medium- sized tiddlywikis. Animations slow it down. Also, if your file gets big you will want to open the shadowed tiddler tab rather than the tab listing all tidders A-Z or by date. Or hide the tabbed menus altogether if you don't need them showing. With each new tiddler, the image of the two tabbed lists I mentioned (all and by date) has to be refreshed and can take a while. You can remove the tabbed lists from the page layout by removing their code from PageTemplate. Nevertheless, I have a couple TiddlyWikis with 1,000s of tiddlers that each have form fields, and I am not noting any other performance issues yet.

The plugin 'load timer' information is available in the shadow tiddler, PluginManager, which is also accessible from the backstage>plugins menu, or by embedding the <<plugins>> macro into any tiddler content.

You can also see the total time taken to load the plugins:

1) go to the tweak dropdown in backstage 2) click the "Show unknown options" checkbox 3) click the "chkDisplayInstrumentation" checkbox, it's about the 8th one down

this will let you see what proportion of the total load time is spent loading the plugins

This section needs to be reviewed and/or refactored to comply with TiddlyWiki.org's quality standards.

This seems to be the constant question: How big can it get? As far as I am aware there is no limit to how big of a file you can download and open. I pumped up a TW to around 3 megs just to see what it could do and didn't have any problems. It took a while to get the file, but I got it.

If you are running lots of plugins then Firefox will give you the "A script is making this page run slow. Do you want to continue?" message, but it will load.

The problems reported by people with large TiddlyWikis are usually performance based, and it seems that the solution (once you've disabled animations..) is to remove macros that loop through every tiddler, like the tabs in the sidebar. So it's not so much the size that's the problem in a direct sense, but the fact that many TW macros assume that looping through every tiddler isn't very slow.